Triple
T10798199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Kuiti |
E254765
|
entity |
| Predicate | distanceFromAuckland |
P90579
|
FINISHED |
| Object | approximately 200 kilometres south |
—
|
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: approximately 200 kilometres south | Statement: [Te Kuiti, distanceFromAuckland, approximately 200 kilometres south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAuckland Context triple: [Te Kuiti, distanceFromAuckland, approximately 200 kilometres south]
-
A.
distanceFromAuckland_km
chosen
Indicates the physical distance, measured in kilometers, between an entity’s location and Auckland.
-
B.
distanceToWellington
Indicates the measured distance between a given entity’s location and the location of Wellington.
-
C.
distanceFromNewZealandMainland_km
Indicates the distance, measured in kilometers, between an entity’s location and the mainland of New Zealand.
-
D.
distanceToPalmerstonNorth
Indicates the spatial distance between a given location and Palmerston North.
-
E.
distanceToChristchurch
Indicates the spatial distance between a given entity’s location and the location of Christchurch.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73334feb08190aae967eaa37659f7 |
completed | April 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.