Triple
T26140736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nine Mile Falls |
E659508
|
entity |
| Predicate | riverMileFromSpokane |
P143635
|
FINISHED |
| Object | approximately nine 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 nine miles | Statement: [Nine Mile Falls, riverMileFromSpokane, approximately nine miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMileFromSpokane Context triple: [Nine Mile Falls, riverMileFromSpokane, approximately nine miles]
-
A.
distanceToSpokaneApprox
chosen
Indicates an approximate distance measurement between a given entity’s location and the city of Spokane.
-
B.
distanceToOlympia
Indicates the measured spatial distance between a given location or object and Olympia.
-
C.
distanceFromTacoma (miles)
Indicates the physical distance, measured in miles, between an entity’s location and the city of Tacoma.
-
D.
riverMilepost
Indicates the specific distance or position along a river, measured in miles from a defined starting point.
-
E.
distanceToReedsport
Indicates the measured distance between a given location and the place named Reedsport.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 26, 2026, 8:20 p.m.