Triple
T34449861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Korokī Kahukura |
E884333
|
entity |
| Predicate | hasAncestralArea |
P90583
|
FINISHED |
| Object | Cambridge |
—
|
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: Cambridge | Statement: [Ngāti Korokī Kahukura, hasAncestralArea, Cambridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralArea Context triple: [Ngāti Korokī Kahukura, hasAncestralArea, Cambridge]
-
A.
hasSiblingArea
Indicates that one area is a sibling of another area, meaning they share the same parent area and are at the same hierarchical level.
-
B.
alsoHasAncestry
Indicates that an entity possesses an additional ancestral lineage or heritage beyond its primary recorded ancestry.
-
C.
hasAncestralLand
chosen
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
D.
hasAncestralIsland
Indicates that an entity has a specific island from which its ancestors originated or to which its lineage is historically tied.
-
E.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 2 a.m.