Triple
T21297955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reardan, Washington |
E524975
|
entity |
| Predicate | distanceToSpokaneApprox |
P143635
|
FINISHED |
| Object | about 20–30 miles west of Spokane |
—
|
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: about 20–30 miles west of Spokane | Statement: [Reardan, Washington, distanceToSpokaneApprox, about 20–30 miles west of Spokane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSpokaneApprox Context triple: [Reardan, Washington, distanceToSpokaneApprox, about 20–30 miles west of Spokane]
-
A.
distanceToSeattle
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
-
B.
distanceToOlympia
Indicates the measured spatial distance between a given location or object and Olympia.
-
C.
distanceToBoise
Indicates the spatial distance between a given entity’s location and the city of Boise.
-
D.
distanceToPortland
Indicates the measured distance between a given location and the city of Portland.
-
E.
distanceFromTacoma (miles)
Indicates the physical distance, measured in miles, between an entity’s location and the city of Tacoma.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385a24d08190bfd410c7f10fa6f7 |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:04 p.m.