Triple
T25077065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Rock |
E628078
|
entity |
| Predicate | distanceToBend |
P88445
|
FINISHED |
| Object | roughly 70 miles southeast of Bend, Oregon |
—
|
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: roughly 70 miles southeast of Bend, Oregon | Statement: [Fort Rock, distanceToBend, roughly 70 miles southeast of Bend, Oregon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBend Context triple: [Fort Rock, distanceToBend, roughly 70 miles southeast of Bend, Oregon]
-
A.
distanceFromBend
chosen
Indicates the spatial distance between a point or segment and a bend or curvature in a path, object, or structure.
-
B.
bendAngle
Indicates the degree to which one part is bent relative to another, typically measured as the angle formed at their joint or intersection.
-
C.
bendLocation
Indicates the location at which something bends, curves, or changes direction.
-
D.
distanceFromBol
Indicates the measured distance between an entity and a specified beginning-of-line (BOL) reference point.
-
E.
distanceToBled
Indicates the spatial distance between a given entity and the location Bled.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 18, 2026, 6:21 a.m.