Triple
T21755570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orting, Washington |
E537028
|
entity |
| Predicate | distanceToTacoma |
P65387
|
FINISHED |
| Object | approximately 20 miles southeast |
—
|
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 20 miles southeast | Statement: [Orting, Washington, distanceToTacoma, approximately 20 miles southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTacoma Context triple: [Orting, Washington, distanceToTacoma, approximately 20 miles southeast]
-
A.
distanceFromTacoma (miles)
chosen
Indicates the physical distance, measured in miles, between an entity’s location and the city of Tacoma.
-
B.
distanceToSeattle
Indicates the measured or calculated distance between a given entity’s location and the city of Seattle.
-
C.
distanceToBellingham
Indicates the measured or estimated distance between a given entity’s location and the location of Bellingham.
-
D.
distanceToOlympia
Indicates the measured spatial distance between a given location or object and Olympia.
-
E.
distanceToPortland
Indicates the measured distance between a given location and the city of Portland.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8d6d0081908e0ccfbccea58895 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.