Triple
T30190809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bellaghy, County Londonderry, Northern Ireland |
E767474
|
entity |
| Predicate | hasTownlandStatus |
P181668
|
FINISHED |
| Object | Bellaghy townland |
—
|
NE NERFINISHED |
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: Bellaghy townland | Statement: [Bellaghy, County Londonderry, Northern Ireland, hasTownlandStatus, Bellaghy townland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTownlandStatus Context triple: [Bellaghy, County Londonderry, Northern Ireland, hasTownlandStatus, Bellaghy townland]
-
A.
hasTownStatus
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
-
B.
hasCivilParishStatus
Indicates that an entity holds the official administrative status or designation of a civil parish.
-
C.
hasMarketTownStatus
Indicates that a settlement holds the official legal or historical status of being recognized as a market town.
-
D.
hasPostalTownStatus
Indicates that an entity holds the official designation or status of being a postal town within a postal addressing system.
-
E.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 29, 2026, 7:28 p.m.