Triple
T4551865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reigate railway station |
E120382
|
entity |
| Predicate | nearbyTownCentreDistance |
P1299
|
FINISHED |
| Object | short walk to Reigate town centre |
—
|
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: short walk to Reigate town centre | Statement: [Reigate railway station, nearbyTownCentreDistance, short walk to Reigate town centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyTownCentreDistance Context triple: [Reigate railway station, nearbyTownCentreDistance, short walk to Reigate town centre]
-
A.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
B.
administrativeCentreNearby
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
-
C.
distanceFromDowntown
chosen
Indicates the physical distance between a given location and the central downtown area.
-
D.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
E.
proximityToLandmark
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd57f7b9748190af29d02fc77b02e0 |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5223423c81908317351b58cff5f5 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.