Triple
T32224402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāpuhi |
E823154
|
entity |
| Predicate | governanceBodyEstablished |
P72356
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [Ngāpuhi, governanceBodyEstablished, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governanceBodyEstablished Context triple: [Ngāpuhi, governanceBodyEstablished, 1980s]
-
A.
governingBodyEstablished
Indicates that a particular governing body was formally created or brought into existence for an entity or domain.
-
B.
governingBodyFoundedIn
chosen
Indicates that a governing body was established or came into official existence in a specified year or time period.
-
C.
governingBodyAtInception
Indicates the organization or authority that served as the governing body of an entity at the time of its creation or founding.
-
D.
governingBodyNameAtTime
Indicates the name of the governing body that held authority over an entity during a specified time period.
-
E.
governingBodyDuringExistence
Indicates that a specific governing body had authority over or administered an entity throughout the period of that entity’s existence.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0041860fd081908623ef9fd40a9775 |
completed | May 10, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_6a00414b01488190a312adb3b25d69cf |
completed | May 10, 2026, 8:26 a.m. |
Created at: May 1, 2026, 12:38 a.m.