Triple
T16954105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amon G. Carter Stadium |
E411251
|
entity |
| Predicate | hasVideoReplay |
P108689
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Amon G. Carter Stadium, hasVideoReplay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVideoReplay Context triple: [Amon G. Carter Stadium, hasVideoReplay, yes]
-
A.
videoReplayUsed
Indicates that a video replay was utilized to review or analyze a prior event or action.
-
B.
usesInstantReplay
Indicates that an entity employs instant replay technology or review during an event, action, or decision process.
-
C.
hasReplay
chosen
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
-
D.
hasVideoRecording
Indicates that there exists an associated video recording capturing or documenting the referenced entity or event.
-
E.
replayFrequency
Indicates how often an event, action, or sequence is repeated or played back over a given period.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d01b04e88190a72735541b3bb117 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.