Triple
T32093484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todd Blackadder |
E819662
|
entity |
| Predicate | coachingRoleEnd |
P174440
|
FINISHED |
| Object | Crusaders head coach 2016 |
—
|
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: Crusaders head coach 2016 | Statement: [Todd Blackadder, coachingRoleEnd, Crusaders head coach 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachingRoleEnd Context triple: [Todd Blackadder, coachingRoleEnd, Crusaders head coach 2016]
-
A.
coachingStart
Indicates the point in time when a coaching relationship or coaching session begins.
-
B.
coachingBase
Indicates a foundational coaching relationship in which one entity serves as the primary coach or mentor for another.
-
C.
coachedRole
Indicates that one entity served as a coach for another entity in a specific role or position.
-
D.
coachingAt
Indicates that one entity is serving as a coach at, or providing coaching services within, a particular organization, institution, or location.
-
E.
coachingTrait
Indicates that one entity possesses a characteristic, style, or quality specifically related to coaching.
- F. None of above. chosen
Provenance (4 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:25 a.m.