Triple
T36439730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanana, Alaska |
E897693
|
entity |
| Predicate | distanceToFairbanks |
P49332
|
FINISHED |
| Object | approximately 130 air miles west |
—
|
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 130 air miles west | Statement: [Tanana, Alaska, distanceToFairbanks, approximately 130 air miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToFairbanks Context triple: [Tanana, Alaska, distanceToFairbanks, approximately 130 air miles west]
-
A.
distanceFromFairbanks
chosen
Indicates the spatial distance between a given location or entity and the city of Fairbanks.
-
B.
distanceFromAnchorage
Indicates the measured distance between a given location or object and Anchorage.
-
C.
approximateDistanceFromAnchorage
Indicates the estimated spatial distance between a given entity and Anchorage, rather than an exact measured value.
-
D.
distanceToTalkeetnaInMiles
Indicates the numerical distance, measured in miles, from a given entity or location to Talkeetna.
-
E.
distanceToKotzebueInMiles
Indicates the numerical distance, measured in miles, between a given entity’s location and Kotzebue.
- F. None of above.
Provenance (3 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_69f76e56636481908eda808ab0273401 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.