Triple
T30653693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homenaje a Dos Leyendas |
E780328
|
entity |
| Predicate | firstEditionHonoree |
P75580
|
FINISHED |
| Object | Salvador Lutteroth |
E780321
|
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: Salvador Lutteroth | Statement: [Homenaje a Dos Leyendas, firstEditionHonoree, Salvador Lutteroth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEditionHonoree Context triple: [Homenaje a Dos Leyendas, firstEditionHonoree, Salvador Lutteroth]
-
A.
firstClassAwardedTo
Indicates that a first-class distinction, honor, or top-level award is given to a particular recipient.
-
B.
honorsPerson
chosen
Indicates that one entity formally recognizes, respects, or pays tribute to a specific person.
-
C.
honoreeKnownFor
Indicates that an honoree is recognized or celebrated specifically for a particular work, achievement, contribution, or notable attribute.
-
D.
yearHonored
Indicates the specific year in which an entity received an honor, award, or formal recognition.
-
E.
honoreeGivenName
Indicates the given (first) name of a person who is being honored or recognized.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a030d3db2748190b32fcf7b21bd0d0a |
completed | May 12, 2026, 11:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2870eec0e08190831f2cc33cd07c41 |
completed | June 9, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_6a030ca6bf388190b2f6931376323da3 |
completed | May 12, 2026, 11:19 a.m. |
Created at: April 29, 2026, 8:30 p.m.