Triple
T31128124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crystal Mountain (Washington) |
E793414
|
entity |
| Predicate | drivingDistanceFromSeattle |
P15605
|
FINISHED |
| Object | approximately 80 miles |
—
|
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 80 miles | Statement: [Crystal Mountain (Washington), drivingDistanceFromSeattle, approximately 80 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingDistanceFromSeattle Context triple: [Crystal Mountain (Washington), drivingDistanceFromSeattle, approximately 80 miles]
-
A.
distanceToSeattle
chosen
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
-
B.
distanceFromTacoma (miles)
Indicates the physical distance, measured in miles, between an entity’s location and the city of Tacoma.
-
C.
distanceToOlympia
Indicates the measured spatial distance between a given location or object and Olympia.
-
D.
distanceToBellingham
Indicates the measured or estimated distance between a given entity’s location and the location of Bellingham.
-
E.
directionFromSeattle
Indicates the cardinal or relative compass direction of an entity’s location measured from Seattle.
- 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.