Triple
T18676878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tackle |
E456622
|
entity |
| Predicate | offensivePlayType |
P132257
|
FINISHED |
| Object | pass play |
—
|
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: pass play | Statement: [The Tackle, offensivePlayType, pass play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensivePlayType Context triple: [The Tackle, offensivePlayType, pass play]
-
A.
offensiveTackle
Indicates that an entity plays the offensive tackle position, responsible for blocking and protecting on the offensive line in a gridiron football context.
-
B.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
C.
offensiveMisplayType
Indicates the specific kind of mistake or error committed by the offensive side during a play or action.
-
D.
playsRoleInOffense
Indicates that an entity performs a specific function or position within an offensive strategy or system.
-
E.
offensiveStrength
Indicates the degree or capacity of an entity to carry out effective attacks or aggressive actions against an opponent.
- 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_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. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:48 a.m.