Triple
T14074833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beast Quake run vs New Orleans Saints |
E338703
|
entity |
| Predicate | playCallType |
P29529
|
FINISHED |
| Object | off-tackle run to the left |
—
|
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: off-tackle run to the left | Statement: [Beast Quake run vs New Orleans Saints, playCallType, off-tackle run to the left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playCallType Context triple: [Beast Quake run vs New Orleans Saints, playCallType, off-tackle run to the left]
-
A.
playCallingStyle
Indicates the characteristic manner or strategic approach an entity uses when selecting and executing plays or actions in a competitive or game-like context.
-
B.
callType
chosen
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
C.
callingStyle
Indicates the manner or convention by which one entity initiates or performs a call or invocation on another entity.
-
D.
playType
Indicates the specific category or style of play or performance associated with an event or action.
-
E.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5bc49881909012b66fa451f495 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.