Triple
T26387372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run and shoot offense |
E663317
|
entity |
| Predicate | typicalBackfieldSet |
P8574
|
FINISHED |
| Object | one-back set |
—
|
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: one-back set | Statement: [Run and shoot offense, typicalBackfieldSet, one-back set]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBackfieldSet Context triple: [Run and shoot offense, typicalBackfieldSet, one-back set]
-
A.
numberOfRunningBacks
Indicates the quantity of running backs involved or associated in the given context or situation.
-
B.
sharedBackfieldWith
Indicates that two players were part of the same offensive backfield unit on a team during overlapping time periods.
-
C.
typicalTeamComposition
Indicates the usual or standard combination of roles or members that make up a team.
-
D.
typicalFormation
chosen
Indicates the usual or characteristic way in which something is formed, structured, or comes into existence.
-
E.
runningBack
Indicates that one entity is acting as a running back in relation to another entity, typically within the context of an American football play or team.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 26, 2026, 11:23 p.m.