Triple
T8013881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt LaFleur |
E186561
|
entity |
| Predicate | coachingTreeOf |
P11640
|
FINISHED |
| Object | Kyle Shanahan coaching tree |
—
|
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: Kyle Shanahan coaching tree | Statement: [Matt LaFleur, coachingTreeOf, Kyle Shanahan coaching tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachingTreeOf Context triple: [Matt LaFleur, coachingTreeOf, Kyle Shanahan coaching tree]
-
A.
coachingTreeIncludes
chosen
Indicates that one coach is part of, or derived from, another coach’s coaching lineage or mentorship hierarchy.
-
B.
movementCoach
Indicates a relationship where one entity serves as a coach or instructor guiding another entity’s physical movement or movement-related skills.
-
C.
conferenceCoach
Indicates a person who provides guidance, training, or mentorship to participants in the context of a conference or similar professional gathering.
-
D.
coachingRecordType
Indicates the specific category or nature of a coaching record associated with an entity or event.
-
E.
coachedFrom
Indicates that one entity served as a coach or trainer for another entity during a specified period or context.
- 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_69ca82abaffc8190ab8af79cdbc31ab3 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df0f4bc8190ae87586972018085 |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:19 p.m.