Triple
T30779172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican National Trios Championship |
E783761
|
entity |
| Predicate | usesChampionshipBelts |
P108713
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mexican National Trios Championship, usesChampionshipBelts, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesChampionshipBelts Context triple: [Mexican National Trios Championship, usesChampionshipBelts, true]
-
A.
SECChampionships
Indicates the number of conference championships an entity has won in the Southeastern Conference (SEC).
-
B.
hasHadMultipleBeltDesigns
Indicates that an entity has undergone more than one distinct belt design over time.
-
C.
hasPhysicalBelt
chosen
Indicates that one entity possesses or is equipped with a physical belt as an item or feature.
-
D.
championshipRecognition
Indicates formal acknowledgment that an entity has won or holds a championship title in a given competition or domain.
-
E.
isFormerChampionshipTrophyOf
Indicates that an object previously served as the official championship trophy awarded for a particular competition or title.
- 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 8:41 p.m.