Triple
T20458401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop Street, Dublin |
E501855
|
entity |
| Predicate | locatedInParishOrArea |
P40
|
FINISHED |
| Object | Dublin 8 inner city area |
—
|
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: Dublin 8 inner city area | Statement: [Bishop Street, Dublin, locatedInParishOrArea, Dublin 8 inner city area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInParishOrArea Context triple: [Bishop Street, Dublin, locatedInParishOrArea, Dublin 8 inner city area]
-
A.
locatedInRegionalDistrict
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
-
B.
isParishSeatOf
Indicates that a location serves as the administrative center or main seat of government for a particular parish.
-
C.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
D.
locatedInCountySeatOfCounty
Indicates that one entity is located in the county seat city or town of the specified county.
-
E.
civilParishIn
Indicates that a civil parish is located within or administratively belongs to a specified larger geographic or governmental area.
- 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_69e0b4ad4940819098cf2ff6413574e5 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696a2a8a88190992211b09295d8ea |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.