Triple
T35636542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Backlash 2016 |
E1029735
|
entity |
| Predicate | titleMatch |
P14366
|
FINISHED |
| Object | WWE World Championship |
—
|
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: WWE World Championship | Statement: [WWE Backlash 2016, titleMatch, WWE World Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleMatch Context triple: [WWE Backlash 2016, titleMatch, WWE World Championship]
-
A.
universalTitleMatch
Indicates that two entities share exactly the same title string across all considered contexts or sources.
-
B.
titlePattern
Indicates that there is a specific structural or textual pattern that the title of an entity is expected to follow.
-
C.
isTitleMatchFor
chosen
Indicates that one entity’s title matches or corresponds to the title of another entity.
-
D.
containsTitle
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
E.
titleCombinesWith
Indicates that one title can be merged or used together with another title to form a combined or composite title.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff878f41888190bcb3bc41ad26081a |
completed | May 9, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69ff854082d88190aad3bfedf05e849f |
completed | May 9, 2026, 7:04 p.m. |
Created at: May 3, 2026, 4:05 p.m.