Triple
T36584636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Whare |
E902488
|
entity |
| Predicate | hasWhakapapa |
P144770
|
FINISHED |
| Object | distinct genealogical traditions |
—
|
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: distinct genealogical traditions | Statement: [Ngāti Whare, hasWhakapapa, distinct genealogical traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWhakapapa Context triple: [Ngāti Whare, hasWhakapapa, distinct genealogical traditions]
-
A.
hasTribalAncestor
Indicates that an entity is descended from, or has lineage tracing back to, a specified tribal ancestor.
-
B.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
C.
hasGenealogy
chosen
Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of another entity.
-
D.
isTāngataWhenuaOf
Indicates that an entity is an indigenous person or people of, and holds ancestral ties and customary authority over, a particular place or land.
-
E.
hasAncestralRoots
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.