Triple
T28350429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denver Nuggets 1980–81 NBA season |
E718078
|
entity |
| Predicate | implementedCoachingStyle |
P29237
|
FINISHED |
| Object | fast-paced 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-paced offense | Statement: [Denver Nuggets 1980–81 NBA season, implementedCoachingStyle, fast-paced offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedCoachingStyle Context triple: [Denver Nuggets 1980–81 NBA season, implementedCoachingStyle, fast-paced offense]
-
A.
coachingTrait
chosen
Indicates that one entity possesses a characteristic, style, or quality specifically related to coaching.
-
B.
hasCoachingStructure
Indicates that one entity provides an organized coaching framework, system, or arrangement for another entity.
-
C.
coachedFormat
Indicates that one entity served as a coach or trainer to another entity in a particular format, style, or structured context.
-
D.
coachedAlongside
Indicates that two or more individuals served as coaches at the same time, typically for the same team, organization, or event.
-
E.
hasCoachingExperienceAs
Indicates that an entity has experience providing coaching in a specified role or capacity.
- 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:45 a.m.