Triple
T11143339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Westport |
E263610
|
entity |
| Predicate | distanceToGreymouth |
P98020
|
FINISHED |
| Object | approximately 100 km |
—
|
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 100 km | Statement: [Westport, distanceToGreymouth, approximately 100 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGreymouth Context triple: [Westport, distanceToGreymouth, approximately 100 km]
-
A.
distanceToPalmerstonNorth
Indicates the spatial distance between a given location and Palmerston North.
-
B.
distanceFromQueenstown
Indicates the measured distance separating a given location or entity from Queenstown.
-
C.
distanceToBlenheim
Indicates the measured distance between a given entity and the location named Blenheim.
-
D.
distanceToChristchurch
Indicates the spatial distance between a given entity’s location and the location of Christchurch.
-
E.
distanceToWellington
Indicates the measured distance between a given entity’s location and the location of Wellington.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8623158819096ad1678fa9e72bb |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:28 p.m.