Triple
T7621215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coldfoot |
E172495
|
entity |
| Predicate | distanceFromArcticOcean |
P78160
|
FINISHED |
| Object | approximately 260 miles 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 260 miles south | Statement: [Coldfoot, distanceFromArcticOcean, approximately 260 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromArcticOcean Context triple: [Coldfoot, distanceFromArcticOcean, approximately 260 miles south]
-
A.
distanceFromArcticCircle
Indicates the measured spatial separation between a given location and the Arctic Circle, typically expressed as a linear or angular distance.
-
B.
distanceToPacificOcean
Indicates the physical distance between a given location or entity and the Pacific Ocean.
-
C.
distanceFromNorthPole
Indicates the measured spatial distance between a given entity’s location and the geographic North Pole.
-
D.
distanceFromCoast
Indicates the measured spatial separation between a location and the nearest point on a coastline.
-
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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6fe7323b0819081664662d2f26937 |
completed | March 27, 2026, 10:02 p.m. |
Created at: March 27, 2026, 3:56 p.m.