Triple
T26009396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rod Brind’Amour |
E646851
|
entity |
| Predicate | roleAsCoach |
P132604
|
FINISHED |
| Object | head coach of the Carolina Hurricanes |
—
|
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: head coach of the Carolina Hurricanes | Statement: [Rod Brind’Amour, roleAsCoach, head coach of the Carolina Hurricanes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAsCoach Context triple: [Rod Brind’Amour, roleAsCoach, head coach of the Carolina Hurricanes]
-
A.
coachedRole
chosen
Indicates that one entity served as a coach for another entity in a specific role or position.
-
B.
playingCoach
Indicates a person who simultaneously serves as both a player and a coach for the same team or organization.
-
C.
conferenceCoach
Indicates a person who provides guidance, training, or mentorship to participants in the context of a conference or similar professional gathering.
-
D.
basedInAsCoach
Indicates that a person holds a coaching position for an organization or team that is located in a specified place.
-
E.
isCoach
Indicates that one entity serves as the coach (trainer or instructor) of another entity.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c698ae48190871cd445422bad91 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 22, 2026, 9:01 a.m.