Triple
T26387408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run and shoot offense |
E663317
|
entity |
| Predicate | typicalPlayType |
P29019
|
FINISHED |
| Object | quick timing routes |
—
|
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: quick timing routes | Statement: [Run and shoot offense, typicalPlayType, quick timing routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPlayType Context triple: [Run and shoot offense, typicalPlayType, quick timing routes]
-
A.
playType
chosen
Indicates the specific category or style of play or performance associated with an event or action.
-
B.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
C.
typicalPlayingPosition
Indicates the usual role or position an entity regularly occupies when participating in a game, sport, or similar activity.
-
D.
isTypicallyPlayed
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
-
E.
typicallyPlays
Indicates that an entity is most commonly or habitually associated with playing a particular role, instrument, position, or type of game.
- 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_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: April 26, 2026, 11:23 p.m.