Triple
T18687418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngāti Whātua |
E456903
|
entity |
| Predicate | urbanIwiInfluence |
P21809
|
FINISHED |
| Object | Auckland urban development |
—
|
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: Auckland urban development | Statement: [Ngāti Whātua, urbanIwiInfluence, Auckland urban development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanIwiInfluence Context triple: [Ngāti Whātua, urbanIwiInfluence, Auckland urban development]
-
A.
hasUrbanInfluence
Indicates that one entity exerts or reflects the characteristics, impact, or style of an urban area on another entity.
-
B.
cityOfInfluence
chosen
Indicates the city that significantly shapes, impacts, or exerts influence over a given entity.
-
C.
influencesCommunity
Indicates that one entity has an effect on the behavior, attitudes, or conditions of a community.
-
D.
alignedUrbanInterestsWith
Indicates that one entity has brought its goals, policies, or actions into strategic agreement with the urban interests, priorities, or agenda of another entity.
-
E.
urbanScale
Indicates the extent or magnitude of development, density, or size at which an area or environment can be characterized as urban.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2e4c6081908bb958bd00d6bec9 |
completed | April 19, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.