Triple
T35364409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorin railway station |
E1021588
|
entity |
| Predicate | distanceToNearbyPlace |
P120034
|
FINISHED |
| Object | approximately 2 km to Chorin Abbey |
—
|
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 km to Chorin Abbey | Statement: [Chorin railway station, distanceToNearbyPlace, approximately 2 km to Chorin Abbey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNearbyPlace Context triple: [Chorin railway station, distanceToNearbyPlace, approximately 2 km to Chorin Abbey]
-
A.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
B.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
C.
distancesFrom
chosen
Indicates the measured spatial separation between one entity and one or more other entities.
-
D.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
E.
infrastructureNearby
Indicates that one entity is located close to another entity that serves as infrastructure (such as roads, utilities, or public facilities).
- 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_69f76def44c881908a20e8008572eb44 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.