Triple
T34218118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matauri Bay, Northland, New Zealand |
E877849
|
entity |
| Predicate | accessedByRoadFrom |
P22549
|
FINISHED |
| Object | Kerikeri |
—
|
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: Kerikeri | Statement: [Matauri Bay, Northland, New Zealand, accessedByRoadFrom, Kerikeri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessedByRoadFrom Context triple: [Matauri Bay, Northland, New Zealand, accessedByRoadFrom, Kerikeri]
-
A.
roadAccessFrom
chosen
Indicates that one location can be reached from another via a usable road connection.
-
B.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
C.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
D.
hasPublicAccessAlongRoad
Indicates that something is accessible to the public from or along an adjacent road.
-
E.
hasAccessRoadsTo
Indicates that there exist one or more roads providing direct vehicular access from one location or site to another.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:55 a.m.