Triple
T27879103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X Division |
E705038
|
entity |
| Predicate | championshipRepresents |
P7458
|
FINISHED |
| Object | Impact X Division Championship |
—
|
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: Impact X Division Championship | Statement: [X Division, championshipRepresents, Impact X Division Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipRepresents Context triple: [X Division, championshipRepresents, Impact X Division Championship]
-
A.
championshipFor
Indicates that a championship event or title is held, awarded, or designated for a particular competition, season, or category.
-
B.
championshipRecognition
Indicates formal acknowledgment that an entity has won or holds a championship title in a given competition or domain.
-
C.
championshipContext
Indicates that the related entities are connected through the context of a championship event, competition, or title.
-
D.
championshipName
Indicates the name or title assigned to a specific championship event or competition.
-
E.
championshipLevel
chosen
Indicates the competitive tier or division in which a championship or title contest is held.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:29 p.m.