Triple
T31535904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoreditch |
E804598
|
entity |
| Predicate | nearbyUndergroundLines |
P33788
|
FINISHED |
| Object | Northern line |
—
|
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: Northern line | Statement: [Shoreditch, nearbyUndergroundLines, Northern line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyUndergroundLines Context triple: [Shoreditch, nearbyUndergroundLines, Northern line]
-
A.
nearUndergroundLine
chosen
Indicates that one entity is located close in distance to an underground (subway/metro) line.
-
B.
subwayServiceAtNearbyStation
Indicates that there is subway service available at a station located near the referenced place or entity.
-
C.
subwayLine
Indicates that there is a subway line connection or service relationship between the referenced entities.
-
D.
nearTramwayLine
Indicates that one entity is located close to a tramway line in physical space.
-
E.
nearbyMainlineConnection
Indicates that one entity has a mainline connection located in close physical proximity to another entity.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 30, 2026, 10:03 p.m.