Triple
T15223603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-formation |
E363820
|
entity |
| Predicate | centerToQuarterbackExchange |
P117594
|
FINISHED |
| Object | direct snap under center |
—
|
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: direct snap under center | Statement: [T-formation, centerToQuarterbackExchange, direct snap under center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerToQuarterbackExchange Context triple: [T-formation, centerToQuarterbackExchange, direct snap under center]
-
A.
associatedWithQuarterback
Indicates a relationship where an entity has a connection, role, or involvement with a quarterback.
-
B.
interceptedQuarterback
Indicates that a defensive player successfully caught a pass thrown by the quarterback, resulting in an interception.
-
C.
JetsQuarterback
Indicates that the subject is a quarterback who plays for, or is associated with, the New York Jets football team.
-
D.
homeQuarterback
Indicates that the subject is the quarterback for the home team in a given game or matchup.
-
E.
playedWithQuarterback
Indicates that one player participated on the same team at the same time as a specific quarterback, sharing game or practice play together.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0078a9318819081db3b7bcc28e04f |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.