Triple
T30653694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homenaje a Dos Leyendas |
E780328
|
entity |
| Predicate | secondLegendAdded |
P195818
|
FINISHED |
| Object | El Santo |
—
|
NE NERFINISHED |
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: El Santo | Statement: [Homenaje a Dos Leyendas, secondLegendAdded, El Santo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondLegendAdded Context triple: [Homenaje a Dos Leyendas, secondLegendAdded, El Santo]
-
A.
secondaryAxis
Indicates a relationship where one axis serves as a secondary or auxiliary reference dimension relative to a primary axis in a coordinate or measurement system.
-
B.
secondSeries
Indicates that one entity is the second installment or season in a series relative to another entity.
-
C.
secondMainFigure
Indicates that an entity serves as the second most important or prominent figure in relation to another primary figure or context.
-
D.
secondedBy
Indicates that an initial proposal, motion, or action by one entity is formally supported or endorsed by another entity as a second.
-
E.
secondCreatedBy
Indicates that an entity was created by a second or subsequent creator, distinguishing this creator from the primary or original one.
- F. None of above. chosen
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_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: April 29, 2026, 8:30 p.m.