Triple
T195099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brad Stevens |
E3800
|
entity |
| Predicate | coachStyle |
P3775
|
FINISHED |
| Object | emphasis on team defense and efficiency |
—
|
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: emphasis on team defense and efficiency | Statement: [Brad Stevens, coachStyle, emphasis on team defense and efficiency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachStyle Context triple: [Brad Stevens, coachStyle, emphasis on team defense and efficiency]
-
A.
coachOf
Indicates that one entity serves as the coach (trainer or manager) of another entity, typically a person or team.
-
B.
styleOfPlay
chosen
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
C.
playerCoachTeam
Indicates a relationship where a player is coached by a specific coach while playing for a particular team.
-
D.
notableCoach
Indicates that one entity is a coach who is widely recognized or distinguished in relation to the other entity.
-
E.
wears
Indicates that one entity is dressed in, or has on its body, a particular item such as clothing or accessories.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25969425081908e178db8ba4631c2 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.