Triple
T24564650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 British & Irish Lions tour to New Zealand |
E607747
|
entity |
| Predicate | kickingCoach |
P133649
|
FINISHED |
| Object | Dave Alred |
—
|
NE NERFINISHED |
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: Dave Alred | Statement: [2005 British & Irish Lions tour to New Zealand, kickingCoach, Dave Alred]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kickingCoach Context triple: [2005 British & Irish Lions tour to New Zealand, kickingCoach, Dave Alred]
-
A.
movementCoach
Indicates a relationship where one entity serves as a coach or instructor guiding another entity’s physical movement or movement-related skills.
-
B.
homeCoach
Indicates that a person serves as the coach of the home team in a particular game or competition.
-
C.
gameCoached
Indicates that one entity served as the coach for another entity in the context of a specific game or match.
-
D.
isCoach
chosen
Indicates that one entity serves as the coach (trainer or instructor) of another entity.
-
E.
conferenceCoach
Indicates a person who provides guidance, training, or mentorship to participants in the context of a conference or similar professional gathering.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f9d0f881909afc04537c32f76b |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.