Triple
T26346598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TNA X Division Championship |
E662790
|
entity |
| Predicate | hasBeenMainEvent |
P167085
|
FINISHED |
| Object | TNA pay-per-view main events |
—
|
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: TNA pay-per-view main events | Statement: [TNA X Division Championship, hasBeenMainEvent, TNA pay-per-view main events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenMainEvent Context triple: [TNA X Division Championship, hasBeenMainEvent, TNA pay-per-view main events]
-
A.
hasMainEventers
Indicates that certain entities are the primary or headline participants in a particular event.
-
B.
hasPrimaryEvent
Indicates that an entity is associated with or linked to its main or most significant event.
-
C.
hasMainPeriod
Indicates that something is associated with or characterized by a primary or most significant time period.
-
D.
hasFormerEvent
Indicates that an entity was preceded by a specific earlier event in its history or sequence.
-
E.
hasSecondaryEvent
Indicates that an entity is associated with an additional, subordinate, or follow-up event linked to a primary event.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 26, 2026, 10:42 p.m.