Triple
T16241665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taranaki iwi |
E394261
|
entity |
| Predicate | iwiAuthorityEstablished |
P122303
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Taranaki iwi, iwiAuthorityEstablished, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iwiAuthorityEstablished Context triple: [Taranaki iwi, iwiAuthorityEstablished, 2006]
-
A.
recognizesAuthority
Indicates that one entity accepts, acknowledges, or submits to the power, control, or legitimate decision-making role of another entity.
-
B.
hasRegistrationAuthority
Indicates that an entity is formally overseen, recorded, or certified by a specific authority responsible for its registration.
-
C.
isWellEstablished
Indicates that something has been firmly recognized, accepted, or validated over time as reliable or authoritative.
-
D.
authorityAffirmedBy
Indicates that the legitimacy or validity of an authority is confirmed, endorsed, or supported by another party or source.
-
E.
hasLegalAuthorityFrom
Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another entity.
- F. None of above. chosen
Provenance (4 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455eeb4c81909066a8af78329ef3 |
completed | April 17, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69e219ee6f6481909663b388dc99770a |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.