Triple
T17449079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Clarendon Street |
E424862
|
entity |
| Predicate | hasRoadNameType |
P62637
|
FINISHED |
| Object | street name |
—
|
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: street name | Statement: [Little Clarendon Street, hasRoadNameType, street name]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadNameType Context triple: [Little Clarendon Street, hasRoadNameType, street name]
-
A.
hasRoadSuffix
Indicates that a road or street name ends with a specific suffix (such as "Street", "Avenue", or "Boulevard").
-
B.
isNamedRoadIn
Indicates that a specific named road is located within or belongs to a particular geographic area or region.
-
C.
hasStreetNameElement
chosen
Indicates that an address or location includes a specific street name component as part of its full designation.
-
D.
hasRoadNumberStatus
Indicates that a road or route is associated with a specific status regarding its assigned road number (e.g., active, reserved, retired, or provisional).
-
E.
hasRoadNetworkType
Indicates the type or classification of road network associated with or present in an 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513b99908190a6b5833559856c8b |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.