Triple
T30397119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāi Tūāhuriri |
E773247
|
entity |
| Predicate | representedWithin |
P194811
|
FINISHED |
| Object | Te Rūnanga o Ngāi Tahu |
—
|
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: Te Rūnanga o Ngāi Tahu | Statement: [Ngāi Tūāhuriri, representedWithin, Te Rūnanga o Ngāi Tahu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedWithin Context triple: [Ngāi Tūāhuriri, representedWithin, Te Rūnanga o Ngāi Tahu]
-
A.
representedUntil
Indicates that an entity served as a representation or proxy for another entity up to a specific point in time, after which it no longer did.
-
B.
representedFrom
Indicates that one entity serves as a representation or depiction of another entity.
-
C.
representedTo
Indicates that one entity formally acted on behalf of or served as the representative of another entity in a given context or interaction.
-
D.
formedWithin
Indicates that one entity was created, established, or came into existence inside the spatial or structural bounds of another entity.
-
E.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: April 29, 2026, 8:03 p.m.