Triple
T22097185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prospect, Oregon |
E546065
|
entity |
| Predicate | distanceToMedfordOregon |
P107939
|
FINISHED |
| Object | approximately 45 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 45 miles | Statement: [Prospect, Oregon, distanceToMedfordOregon, approximately 45 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMedfordOregon Context triple: [Prospect, Oregon, distanceToMedfordOregon, approximately 45 miles]
-
A.
distanceToMedford
chosen
Indicates the spatial distance between a given location or object and the place named Medford.
-
B.
distanceToPortland
Indicates the measured distance between a given location and the city of Portland.
-
C.
distanceFromSalem
Indicates the measured spatial distance between a given entity and the location Salem.
-
D.
distanceToAstoria, Oregon
Indicates the measured distance between a given location and Astoria, Oregon.
-
E.
distanceToPortlandMaine
Indicates the physical distance between a given location and the city of Portland, Maine.
- 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128ea00d48190b020aba80dcdbec9 |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.