Triple
T27308616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chichester Street |
E689135
|
entity |
| Predicate | hasRoadHierarchyRole |
P145907
|
FINISHED |
| Object | city centre distributor street |
—
|
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: city centre distributor street | Statement: [Chichester Street, hasRoadHierarchyRole, city centre distributor street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadHierarchyRole Context triple: [Chichester Street, hasRoadHierarchyRole, city centre distributor street]
-
A.
hasStreetHierarchyRole
chosen
Indicates that an entity holds a specific functional or positional role within a defined street hierarchy.
-
B.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an entity.
-
C.
hasRoadClass
Indicates that a road segment is assigned to a particular classification or category based on its type or functional importance.
-
D.
hasRoadComponent
Indicates that something includes, contains, or is composed of a specific road-related part or element.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 11:26 a.m.