Triple
T26482157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECW World Tag Team Championship |
E664716
|
entity |
| Predicate | becameWorldTitle |
P50937
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [ECW World Tag Team Championship, becameWorldTitle, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameWorldTitle Context triple: [ECW World Tag Team Championship, becameWorldTitle, 1994]
-
A.
resultedInFirstWorldTitleFor
Indicates that one entity’s achievement, event, or action caused another entity to obtain its first world championship title.
-
B.
wonWorldTitleIn
Indicates that an entity achieved victory in a world championship title in a specified competition or year.
-
C.
worldChampionTitleStart
chosen
Indicates the point in time when an entity first attains a world champion title in a given domain or competition.
-
D.
heldWorldsLargestTitleFrom
Indicates that an entity held the distinction of being the world’s largest in a particular category starting from a specified time.
-
E.
hasNotableTitleHolderWhoBecame
Indicates that an entity has a notable title holder who later attained or transitioned into another specified role, status, or position.
- 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.