Triple
T31429837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys 1990s Super Bowl dynasty |
E801764
|
entity |
| Predicate | keyDefensiveEnd |
P36659
|
FINISHED |
| Object | Charles Haley |
—
|
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: Charles Haley | Statement: [Dallas Cowboys 1990s Super Bowl dynasty, keyDefensiveEnd, Charles Haley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyDefensiveEnd Context triple: [Dallas Cowboys 1990s Super Bowl dynasty, keyDefensiveEnd, Charles Haley]
-
A.
defensiveEnd
chosen
Indicates a relationship where an entity plays or serves in the role of a defensive end in a defensive formation or system.
-
B.
defensiveTackle
Indicates that an entity plays the defensive tackle position, typically lining up on the interior of the defensive line to disrupt offensive plays.
-
C.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
D.
primaryDefensiveLine
Indicates the main line of defense that first engages or protects against an opposing force or threat.
-
E.
defensiveSide
Indicates which entity is acting in a defensive role or position relative to another entity or situation.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 8:56 p.m.