Triple
T6389144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyttelton |
E143773
|
entity |
| Predicate | distanceToChristchurch |
P70323
|
FINISHED |
| Object | approximately 12 km southeast |
—
|
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 12 km southeast | Statement: [Lyttelton, distanceToChristchurch, approximately 12 km southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToChristchurch Context triple: [Lyttelton, distanceToChristchurch, approximately 12 km southeast]
-
A.
distanceToWellington
Indicates the measured distance between a given entity’s location and the location of Wellington.
-
B.
distanceToPalmerstonNorth
Indicates the spatial distance between a given location and Palmerston North.
-
C.
distanceFromNewZealandMainland_km
Indicates the distance, measured in kilometers, between an entity’s location and the mainland of New Zealand.
-
D.
distanceFromSantiago
Indicates the spatial distance between a given entity and the location of Santiago.
-
E.
distanceToSantiago_km
Indicates the physical distance, measured in kilometers, between a given location and Santiago.
- F. None of above. chosen
Provenance (4 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0686cc6d481909c62a29a84a4ce8e |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.