Triple
T31134163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auke Bay |
E793591
|
entity |
| Predicate | distanceFromDowntownJuneau |
P203553
|
FINISHED |
| Object | approximately 12 miles northwest |
—
|
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 miles northwest | Statement: [Auke Bay, distanceFromDowntownJuneau, approximately 12 miles northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDowntownJuneau Context triple: [Auke Bay, distanceFromDowntownJuneau, approximately 12 miles northwest]
-
A.
distanceFromAnchorage
Indicates the measured distance between a given location or object and Anchorage.
-
B.
approximateDistanceFromAnchorage
Indicates the estimated spatial distance between a given entity and Anchorage, rather than an exact measured value.
-
C.
distanceFromKetchikan
Indicates the spatial distance between a given location and the city of Ketchikan.
-
D.
distanceTo Juneau (approximate, by air)
Indicates the approximate straight-line (air) distance between a given location and Juneau.
-
E.
relativeLocationToAnchorage
Indicates a spatial relationship specifying where something is located in relation to Anchorage as a reference point.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01a23d8b148190ac2c8765aa9227c4 |
completed | May 11, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_6a01a1e8bb90819096647e929bfb3db8 |
completed | May 11, 2026, 9:31 a.m. |
| PDg | Predicate description generation | batch_6a01a23ce3b08190acb03793824baf68 |
completed | May 11, 2026, 9:32 a.m. |
Created at: April 29, 2026, 9:05 p.m.