Triple
T17635466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ropley railway station |
E430081
|
entity |
| Predicate | distanceFromAlresford |
P128351
|
FINISHED |
| Object | approximately 2.5 miles west |
—
|
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 2.5 miles west | Statement: [Ropley railway station, distanceFromAlresford, approximately 2.5 miles west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAlresford Context triple: [Ropley railway station, distanceFromAlresford, approximately 2.5 miles west]
-
A.
distanceFromSalem
Indicates the measured spatial distance between a given entity and the location Salem.
-
B.
distanceToReedsport
Indicates the measured distance between a given location and the place named Reedsport.
-
C.
distanceFromReno
Indicates the spatial distance between a given entity and the location Reno.
-
D.
distanceToOgden
Indicates the spatial distance between an entity and the location named Ogden.
-
E.
distanceToEugene
Indicates the spatial distance between a given entity and the location named Eugene.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46de0ad988190b1a2c0bff69eb9f1 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cddc87188190ac2f049b86038676 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:52 a.m.