Triple
T17422273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasilla, Alaska |
E423644
|
entity |
| Predicate | distanceToAnchorageMiles |
P43986
|
FINISHED |
| Object | approximately 43 miles by road |
—
|
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 43 miles by road | Statement: [Wasilla, Alaska, distanceToAnchorageMiles, approximately 43 miles by road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAnchorageMiles Context triple: [Wasilla, Alaska, distanceToAnchorageMiles, approximately 43 miles by road]
-
A.
distanceFromAnchorage
chosen
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.
distanceFromFairbanks
Indicates the spatial distance between a given location or entity and the city of Fairbanks.
-
D.
approximateDistanceFromSeward
Indicates the estimated spatial distance between a given entity and the location of Seward.
-
E.
distanceToAlaskaApproxKm
Indicates the approximate distance, measured in kilometers, between a given entity’s location and the state of Alaska.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44237f2cc819083ca0e7e00d828fb |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.