Triple
T23420025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Choke |
E560624
|
entity |
| Predicate | offensiveSystemOfOilers |
P25454
|
FINISHED |
| Object | run-and-shoot offense |
—
|
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: run-and-shoot offense | Statement: [The Choke, offensiveSystemOfOilers, run-and-shoot offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensiveSystemOfOilers Context triple: [The Choke, offensiveSystemOfOilers, run-and-shoot offense]
-
A.
offensiveStrategy
chosen
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
B.
usedOffensiveSystem
Indicates that an entity employed an offensive system (such as a weapon or attack mechanism) against another entity or target.
-
C.
offensiveCoach
Indicates that one entity serves as the offensive coach (responsible for directing the offense) for another entity, typically a sports team or player.
-
D.
offensiveCharacteristic
Indicates that one entity possesses a trait, behavior, or quality that is considered insulting, disrespectful, or likely to cause offense to another entity or group.
-
E.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54489d48190b2b2c29701851765 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:44 p.m.