Triple
T26346544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Hardcore Championship |
E662789
|
entity |
| Predicate | unificationMatchLoser |
P160995
|
FINISHED |
| Object | Tommy Dreamer |
—
|
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: Tommy Dreamer | Statement: [WWE Hardcore Championship, unificationMatchLoser, Tommy Dreamer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unificationMatchLoser Context triple: [WWE Hardcore Championship, unificationMatchLoser, Tommy Dreamer]
-
A.
unificationMatchWinner
chosen
Indicates that an entity is the winner of a unification match between two or more competing entities.
-
B.
loserParty
Indicates that a particular political party was the one that lost in a given election or contest.
-
C.
unificationType
Indicates the specific manner or category in which two or more entities are combined, merged, or treated as a single unified whole.
-
D.
unificationPossible
Indicates that two entities can be combined or reconciled into a single, consistent representation under a shared set of constraints or rules.
-
E.
featuredMatchLoser
Indicates that an entity is the participant who lost in a designated featured match.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 10:42 p.m.