Triple
T23900020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys Doomsday Defense |
E601014
|
entity |
| Predicate | Doomsday IIKeyPlayer |
P154000
|
FINISHED |
| Object | Randy White |
—
|
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: Randy White | Statement: [Dallas Cowboys Doomsday Defense, Doomsday IIKeyPlayer, Randy White]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Doomsday IIKeyPlayer Context triple: [Dallas Cowboys Doomsday Defense, Doomsday IIKeyPlayer, Randy White]
-
A.
hasSecondaryProtagonist
Indicates that an entity (such as a work of fiction) features another character who serves as a secondary or supporting main protagonist alongside the primary one.
-
B.
أُلغي
Indicates that an action, event, or arrangement has been canceled or annulled.
-
C.
secondBoom
Indicates that a second explosive event or major impactful occurrence happens following an initial one.
-
D.
Invoker
Indicates that one entity initiates or triggers an action, process, or event involving another entity.
-
E.
secondEditionChampion
Indicates that an entity is the champion or winner of the second edition or iteration of a particular event, competition, or series.
- F. None of above. chosen
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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:26 p.m.