Triple
T15184553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islington–City Centre West |
E362832
|
entity |
| Predicate | isSuburbanCentre |
P90558
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Islington–City Centre West, isSuburbanCentre, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuburbanCentre Context triple: [Islington–City Centre West, isSuburbanCentre, true]
-
A.
isSuburbanArea
Indicates that a location is characterized as a suburban area, typically lying between urban and rural regions and exhibiting suburban development patterns.
-
B.
isSuburbanMunicipality
Indicates that a municipality is located in a suburban area, typically surrounding or adjacent to a larger urban center.
-
C.
isSuburbanCommunity
Indicates that a community is located in a suburban area, typically characterized by residential neighborhoods situated between urban centers and rural regions.
-
D.
isInSuburbanArea
Indicates that something is located within a suburban area, typically between urban and rural regions.
-
E.
isSuburbanHub
chosen
Indicates that a location functions as a primary activity or transit center within a suburban area, serving surrounding neighborhoods.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006674c088190ba635a78c30f5637 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.