Triple
T38334049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michelle McCool |
E1037901
|
entity |
| Predicate | firstToUnifyTitles |
P122456
|
FINISHED |
| Object | WWE Women’s and Divas Championships |
E385134
|
NE 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 Women’s and Divas Championships | Statement: [Michelle McCool, firstToUnifyTitles, WWE Women’s and Divas Championships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstToUnifyTitles Context triple: [Michelle McCool, firstToUnifyTitles, WWE Women’s and Divas Championships]
-
A.
firstTitleFor
Indicates that one entity is the earliest or primary title assigned to another entity, typically among multiple possible titles.
-
B.
firstTitleSince
Indicates that an entity has achieved a particular title for the first time since a specified earlier point, event, or prior title occurrence.
-
C.
firstUseAsTitleBy
Indicates that an entity is the first to use a given term, phrase, or designation as a formal title for another entity.
-
D.
earlyTitleOf
Indicates that one entity served as an earlier or preliminary title for another entity.
-
E.
unitedWithTitle
chosen
Indicates that an entity has been joined or merged with another entity under a shared or combined title.
- F. None of above.
Provenance (4 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41cc9748fc81909b5494ecffe84cbb |
completed | June 29, 2026, 1:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.