Triple
T29441408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Dover Street |
E746721
|
entity |
| Predicate | hasSideStreetConnection |
P36837
|
FINISHED |
| Object | Long Lane |
—
|
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: Long Lane | Statement: [Great Dover Street, hasSideStreetConnection, Long Lane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideStreetConnection Context triple: [Great Dover Street, hasSideStreetConnection, Long Lane]
-
A.
hasConnectingStreet
chosen
Indicates that two locations are linked by a street that directly connects them.
-
B.
hasSideStreetType
Indicates that an entity (such as a street or road segment) is associated with a specific type or classification of side street.
-
C.
hasSideStreetRole
Indicates that an entity holds a specific functional or contextual role in relation to a side street.
-
D.
isSideStreetOf
Indicates that one street is a smaller, less prominent road that connects to or branches off from another main street.
-
E.
hasSideStreetCharacter
Indicates that something (typically a location or area) possesses the qualities or atmosphere characteristic of a side street, such as being smaller, less prominent, or more intimate than main thoroughfares.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 28, 2026, 3:22 p.m.