Triple
T5581858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brendon McCullum |
E146657
|
entity |
| Predicate | coachingRoleStartYearWithEnglandTestTeam |
P7106
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Brendon McCullum, coachingRoleStartYearWithEnglandTestTeam, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coachingRoleStartYearWithEnglandTestTeam Context triple: [Brendon McCullum, coachingRoleStartYearWithEnglandTestTeam, 2022]
-
A.
joinedTeamAsCoachYear
Indicates the year in which an individual joined a team specifically in the role of coach.
-
B.
teamCoachedFromTo
Indicates a coaching relationship where a person served as coach of a team during a specific time interval from a start date to an end date.
-
C.
yearsActiveAsCoach
Indicates the span of time, typically in years, during which an individual has served in a coaching role.
-
D.
beganUnderCoach
Indicates that one entity started its activity, career, or involvement while being coached or supervised by another entity.
-
E.
headCoachStartYear
chosen
Indicates the year in which an individual began serving as the head coach of a team or organization.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208147a48190b2cdb42b9c9814a3 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.