Triple
T35824250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La malasangre |
E1035590
|
entity |
| Predicate | notableProductionBy |
P190988
|
FINISHED |
| Object | Cristina Banegas |
E317886
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Cristina Banegas | Statement: [La malasangre, notableProductionBy, Cristina Banegas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProductionBy Context triple: [La malasangre, notableProductionBy, Cristina Banegas]
-
A.
notableProductionFor
Indicates that an entity is especially well-known or recognized for producing or creating another specified entity.
-
B.
notableShowProduced
Indicates that an entity played a significant role in producing a show that is considered notable.
-
C.
notableProductionType
Indicates that the subject is particularly known for producing or creating instances of the specified type.
-
D.
notableWorkFeaturing
Indicates that a particular notable work (such as a book, film, or artwork) prominently includes, showcases, or is centered around a given entity.
-
E.
notableProductionPresented
chosen
Indicates that a particular production has been prominently presented or staged by a given entity, such as a venue, company, or organization.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e185ffc8190880b3cdf51decd38 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a425eb829e08190b149584323b9a99f |
completed | June 29, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.