Triple
T17915435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Āti Awa |
E447913
|
entity |
| Predicate | hasAncestralTiesTo |
P34787
|
FINISHED |
| Object | Taranaki |
—
|
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: Taranaki | Statement: [Te Āti Awa, hasAncestralTiesTo, Taranaki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralTiesTo Context triple: [Te Āti Awa, hasAncestralTiesTo, Taranaki]
-
A.
hasAncestralRoots
chosen
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
-
B.
ancestralLinks
Indicates a genealogical relationship where one entity is an ancestor of, or connected through a line of descent to, another entity.
-
C.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
E.
hasMatrilinealConnection
Indicates a relationship where one entity is connected to another through a line of descent traced exclusively through female ancestors.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a3054f048190a98a3b314cd82d5c |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:20 a.m.