Triple
T27450893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Street |
E692435
|
entity |
| Predicate | correspondsToStreetType |
P165387
|
FINISHED |
| Object | major urban thoroughfare |
—
|
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: major urban thoroughfare | Statement: [King’s Street, correspondsToStreetType, major urban thoroughfare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToStreetType Context triple: [King’s Street, correspondsToStreetType, major urban thoroughfare]
-
A.
hasStreetNamingPattern
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
B.
isNumberedStreet
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
C.
hasSideStreetType
Indicates that an entity (such as a street or road segment) is associated with a specific type or classification of side street.
-
D.
hasStreetDirection
Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
-
E.
cityStreetUsed
Indicates that a particular city street is utilized or traversed in the course of some activity, route, or event.
- 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_69ef5206c9248190b5975c2a7f9d229c |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 12:47 p.m.