Triple
T2137475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dave Gallaher Trophy |
E46687
|
entity |
| Predicate | namedForRoleOfHonouree |
P18120
|
FINISHED |
| Object | former All Blacks captain |
—
|
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: former All Blacks captain | Statement: [Dave Gallaher Trophy, namedForRoleOfHonouree, former All Blacks captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForRoleOfHonouree Context triple: [Dave Gallaher Trophy, namedForRoleOfHonouree, former All Blacks captain]
-
A.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
B.
ceremonialRole
Indicates that an entity holds a formal, often symbolic or honorific, position or function within a ceremony or ritual context.
-
C.
honoursSystemRole
Indicates that one entity respects, preserves, or correctly applies the designated system-level role of another entity or process.
-
D.
hasNotableHonoree
Indicates that an entity is notably dedicated to, named after, or honors a particular person or group.
-
E.
honouredPersonOccupation
chosen
Indicates that the honored person is or was associated with a particular occupation or professional role.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.