Triple
T4920706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TT |
E110456
|
entity |
| Predicate | reasonForWorldChampionshipRemoval |
P10714
|
FINISHED |
| Object | safety concerns |
—
|
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: safety concerns | Statement: [TT, reasonForWorldChampionshipRemoval, safety concerns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForWorldChampionshipRemoval Context triple: [TT, reasonForWorldChampionshipRemoval, safety concerns]
-
A.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
-
B.
hasWorldChampionship
Indicates that an entity possesses, has won, or holds a world championship title or status.
-
C.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
-
D.
defendingChampionEliminatedIn
Indicates that the defending champion of a competition was eliminated in a specified round, stage, or edition of that competition.
-
E.
reasonForDisqualification
chosen
Indicates the specific cause or justification for which an entity was deemed ineligible or disqualified from consideration or participation.
- 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_69bd4413f9908190afcff44d7929cc4c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:30 p.m.