Triple
T18927748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanisivik |
E463017
|
entity |
| Predicate | distanceToArcticBay |
P133830
|
FINISHED |
| Object | approximately 28 kilometres |
—
|
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 28 kilometres | Statement: [Nanisivik, distanceToArcticBay, approximately 28 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToArcticBay Context triple: [Nanisivik, distanceToArcticBay, approximately 28 kilometres]
-
A.
distanceFromArcticCircle
Indicates the measured spatial separation between a given location and the Arctic Circle, typically expressed as a linear or angular distance.
-
B.
distanceFromArcticOcean
Indicates the measured spatial distance between a given entity and the Arctic Ocean.
-
C.
distanceFromFairbanks
Indicates the spatial distance between a given location or entity and the city of Fairbanks.
-
D.
distanceToIqaluit
Indicates the spatial distance between a given entity’s location and the location of Iqaluit.
-
E.
distanceToAlaskaApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and the state of Alaska.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9bdddb481908bebd32f927ed5de |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.