Triple
T10981106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary Kubiak |
E259505
|
entity |
| Predicate | styleOfPlayOrWork |
P3775
|
FINISHED |
| Object | West Coast offense principles |
—
|
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: West Coast offense principles | Statement: [Gary Kubiak, styleOfPlayOrWork, West Coast offense principles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfPlayOrWork Context triple: [Gary Kubiak, styleOfPlayOrWork, West Coast offense principles]
-
A.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
B.
notableWorkStyle
Indicates a stylistic characteristic or distinctive manner associated with a notable work created by the subject.
-
C.
hasWorkStyle
Indicates the type or manner in which an entity typically performs work or carries out tasks.
-
D.
performanceStyle
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
E.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772ea940c8190ab3e62e89244f954 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.