Triple
T26021916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Richmond Road |
E647172
|
entity |
| Predicate | isThoroughfareIn |
P106509
|
FINISHED |
| Object | Putney |
—
|
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: Putney | Statement: [Lower Richmond Road, isThoroughfareIn, Putney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isThoroughfareIn Context triple: [Lower Richmond Road, isThoroughfareIn, Putney]
-
A.
isNamedRoadIn
chosen
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
B.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
C.
isSideStreetOf
Indicates that one street is a smaller, less prominent road that connects to or branches off from another main street.
-
D.
isNumberedAvenueOf
Indicates that one entity is an avenue identified by a numerical designation that belongs to or is part of the other entity (such as a city or road network).
-
E.
isInnerCityRoad
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
- 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_69e77e8aa65881909ca58918f29ab2a0 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605e6cc1c8190a5379dbddee008a3 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:04 a.m.