Triple
T18676897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tackle |
E456622
|
entity |
| Predicate | yardLineOfTackle |
P49536
|
FINISHED |
| Object | 1-yard line |
—
|
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: 1-yard line | Statement: [The Tackle, yardLineOfTackle, 1-yard line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yardLineOfTackle Context triple: [The Tackle, yardLineOfTackle, 1-yard line]
-
A.
lineOfScrimmage
Indicates the position on the field where the ball is placed and play begins, separating the offensive and defensive sides before the snap.
-
B.
interceptionYardLine
Indicates the yard line on the field where an interception occurs during a play.
-
C.
yardLine
chosen
Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
-
D.
defensiveLineAlong
Indicates a spatial relationship where a defensive formation or barrier is arranged along the length or path of a specified line or boundary.
-
E.
defensiveLineTargeted
Indicates that a specific defensive line or its players are the intended focus of an offensive play, strategy, or action.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b66680819082a268f1bf857db5 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.