Triple
T33384209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Kurī |
E854867
|
entity |
| Predicate | trustBoardEstablished |
P176829
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Ngāti Kurī, trustBoardEstablished, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trustBoardEstablished Context triple: [Ngāti Kurī, trustBoardEstablished, 1988]
-
A.
trustedStatus
Indicates that one entity regards another as reliable, dependable, or worthy of confidence in a given context.
-
B.
trustModel
Indicates that one entity relies on or has confidence in the reliability, integrity, or performance of another entity or system.
-
C.
trustAnchoredVia
Indicates that a relationship of trust is established or justified through a specific intermediary or anchoring mechanism (such as a trusted authority, key, or certificate).
-
D.
hasTrust
Indicates that one entity has confidence in the reliability, integrity, or good intentions of another entity.
-
E.
establishedThrough
Indicates that a relationship, structure, or state comes into existence or is formally created by means of a specified process, action, or intermediary.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6f37f36ac8190b1bff8711d6771cb |
completed | May 3, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:35 a.m.