Triple
T36447525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Takapūwāhia Marae |
E897916
|
entity |
| Predicate | primaryMaraeOf |
P37005
|
FINISHED |
| Object | Ngāti Toa Rangatira |
E260121
|
NE 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: Ngāti Toa Rangatira | Statement: [Takapūwāhia Marae, primaryMaraeOf, Ngāti Toa Rangatira]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMaraeOf Context triple: [Takapūwāhia Marae, primaryMaraeOf, Ngāti Toa Rangatira]
-
A.
hasMarae
chosen
Indicates a relationship where an entity possesses, contains, or is associated with a marae (a Māori meeting place or communal space).
-
B.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
-
C.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
principalMonasteryOf
Indicates that one monastery serves as the main or most important monastery associated with another entity (such as an order, region, or institution).
-
E.
majorTempleLocation
Indicates that a major temple associated with an entity is located at a specified place.
- F. None of above.
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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41cc8b15d08190a8c56e9ec6343039 |
completed | June 29, 2026, 1:38 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.