Triple
T26482176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECW World Tag Team Championship |
E664716
|
entity |
| Predicate | vacatedDueTo |
P20519
|
FINISHED |
| Object | injuries |
—
|
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: injuries | Statement: [ECW World Tag Team Championship, vacatedDueTo, injuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vacatedDueTo Context triple: [ECW World Tag Team Championship, vacatedDueTo, injuries]
-
A.
vacatedWhen
Indicates the time or date at which something (such as a position, office, or place) was given up, left, or no longer occupied.
-
B.
vacatingBody
Indicates that one entity is leaving, withdrawing from, or giving up its position, role, or occupancy in relation to another entity.
-
C.
fledDueTo
Indicates that one entity escaped or ran away because of, or in response to, another entity or specific cause.
-
D.
abandonedReason
chosen
Indicates the reason or cause for which something was abandoned, discontinued, or given up.
-
E.
retreatCause
Indicates that one event, condition, or factor serves as the reason or trigger for a retreat by an entity.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612fbdb1c8190a837de40747d6b53 |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:28 a.m.