Triple
T32170566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokomaru |
E821698
|
entity |
| Predicate | iwiContext |
P2919
|
FINISHED |
| Object | Ngāpuhi |
—
|
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: Ngāpuhi | Statement: [Tokomaru, iwiContext, Ngāpuhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iwiContext Context triple: [Tokomaru, iwiContext, Ngāpuhi]
-
A.
unitContext
Indicates the contextual framework or setting (such as scope, conditions, or environment) within which a particular unit, instance, or occurrence is defined or interpreted.
-
B.
contextOf
chosen
Indicates that one entity provides the situational, informational, or environmental background within which another entity exists, occurs, or is interpreted.
-
C.
integrationContext
Indicates the contextual framework or environment within which multiple components, systems, or processes are combined and interact as an integrated whole.
-
D.
contextName
Indicates the specific contextual label or identifier under which an entity, event, or relation is defined or interpreted.
-
E.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
- 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_69f3490699a48190bbef96b198e8fade |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba75252c8190991e0bb2c6452745 |
completed | May 3, 2026, 3:01 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:33 a.m.