Triple
T26277563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāi Tahu Holdings |
E660614
|
entity |
| Predicate | affiliatedPeople |
P77482
|
FINISHED |
| Object | Ngāi Tahu tribal members |
—
|
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: Ngāi Tahu tribal members | Statement: [Ngāi Tahu Holdings, affiliatedPeople, Ngāi Tahu tribal members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliatedPeople Context triple: [Ngāi Tahu Holdings, affiliatedPeople, Ngāi Tahu tribal members]
-
A.
associatedPersonField
Indicates that there is a person linked or connected to the subject in a relevant or contextual way.
-
B.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
C.
peopleAssociatedWith
chosen
Indicates that there exists some form of connection, involvement, or relationship between the referenced people.
-
D.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
E.
relatedTeam
Indicates that two teams are connected or associated with each other in a relevant or meaningful way.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60e3641208190af80d23f7a692f3e |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:57 p.m.