Triple
T6547495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campeón de Campeones |
E151046
|
entity |
| Predicate | determinesTitle |
P66163
|
FINISHED |
| Object | overall national super champion of Mexico |
—
|
LITERAL 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: overall national super champion of Mexico | Statement: [Campeón de Campeones, determinesTitle, overall national super champion of Mexico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determinesTitle Context triple: [Campeón de Campeones, determinesTitle, overall national super champion of Mexico]
-
A.
decidesTitle
Indicates that one entity determines or selects the official title or name assigned to another entity.
-
B.
titleDeciderFor
chosen
Indicates that one entity is responsible for determining or assigning the title associated with another entity.
-
C.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
D.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
E.
recognizesTitle
Indicates that one entity acknowledges or accepts another entity’s formal title or designation as valid or appropriate.
- F. None of above.
Provenance (3 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:50 p.m.