Triple
T17836317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl's Court Road |
E445395
|
entity |
| Predicate | hasSideStreetRole |
P129365
|
FINISHED |
| Object | access to residential properties |
—
|
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: access to residential properties | Statement: [Earl's Court Road, hasSideStreetRole, access to residential properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideStreetRole Context triple: [Earl's Court Road, hasSideStreetRole, access to residential properties]
-
A.
hasSideStreetType
Indicates that an entity (such as a street or road segment) is associated with a specific type or classification of side street.
-
B.
hasSecondaryStreet
Indicates that an entity is associated with an additional, non-primary street address or roadway.
-
C.
hasConnectingStreet
Indicates that two locations are linked by a street that directly connects them.
-
D.
hasNearbyStreet
Indicates that one entity is located close to or adjacent to a street.
-
E.
hasStreet
Indicates that an entity is located on, associated with, or identified by a particular street.
- F. None of above. chosen
Provenance (4 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d27f8908190bf48a8153756effa |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:16 a.m.