Triple
T35628430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elimination Chamber 2019 |
E1029518
|
entity |
| Predicate | hadMatch |
P127214
|
FINISHED |
| Object | WWE Championship Elimination Chamber match |
—
|
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: WWE Championship Elimination Chamber match | Statement: [Elimination Chamber 2019, hadMatch, WWE Championship Elimination Chamber match]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMatch Context triple: [Elimination Chamber 2019, hadMatch, WWE Championship Elimination Chamber match]
-
A.
hasMatch
chosen
Indicates that one entity corresponds to, aligns with, or is considered an equivalent or suitable counterpart to another entity.
-
B.
mayMatch
Indicates a potential or permissible correspondence or pairing between two entities, without guaranteeing that the match actually occurs.
-
C.
hadNo
Indicates that one entity completely lacked or did not possess another entity, attribute, or relationship.
-
D.
hasFinalMatch
Indicates that an entity is associated with a concluding or decisive match in a series, tournament, or competition.
-
E.
hadIndex
Indicates that one entity possessed or was associated with a particular index (such as a numerical or reference position) at a given time or in a given context.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.