Triple
T37890689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludgate Hill railway station |
E945123
|
entity |
| Predicate | nearbyThoroughfare |
P8235
|
FINISHED |
| Object | Farringdon Street |
—
|
NE NERFINISHED |
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: Farringdon Street | Statement: [Ludgate Hill railway station, nearbyThoroughfare, Farringdon Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyThoroughfare Context triple: [Ludgate Hill railway station, nearbyThoroughfare, Farringdon Street]
-
A.
nearbyMajorRoad
Indicates that one entity is located close to a significant or heavily used road.
-
B.
hasNearbyStreet
chosen
Indicates that one entity is located close to or adjacent to a street.
-
C.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
-
D.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
E.
isThoroughfareFor
Indicates that something serves as a route or passageway used for travel or transportation between places.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.