Triple
T9161792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack McKinney |
E219840
|
entity |
| Predicate | strategyDeveloped |
P73
|
FINISHED |
| Object | fast-break oriented 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: fast-break oriented offense | Statement: [Jack McKinney, strategyDeveloped, fast-break oriented offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strategyDeveloped Context triple: [Jack McKinney, strategyDeveloped, fast-break oriented offense]
-
A.
strategyDesigner
Indicates that one entity is responsible for creating or formulating strategies for another entity or context.
-
B.
strategyType
Indicates the specific kind or category of strategy associated with an entity or action.
-
C.
aimsToDevelop
Indicates an entity’s intention or effort to create, improve, or bring about another entity, outcome, or capability.
-
D.
strategyComponent
Indicates that one element functions as a constituent or building block within a broader strategy.
-
E.
developed
chosen
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2c1a9881909b7100b6e436386d |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:21 p.m.