Triple
T9820065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaeltacht of Meath |
E238505
|
entity |
| Predicate | regionServes |
P30177
|
FINISHED |
| Object | Irish-language speakers in County Meath |
—
|
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: Irish-language speakers in County Meath | Statement: [Gaeltacht of Meath, regionServes, Irish-language speakers in County Meath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionServes Context triple: [Gaeltacht of Meath, regionServes, Irish-language speakers in County Meath]
-
A.
regionServedFromHub
Indicates that a particular region receives its services, operations, or logistical support from a specified hub location.
-
B.
servesRegionAcrossFrom
Indicates that a service or entity operates in a region that is geographically located directly across from another specified region.
-
C.
regionSub
Indicates that one region is a subregion or contained part of another, larger region.
-
D.
serviceRegion
chosen
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
E.
cityServedRegion
Indicates that a city provides services to, or functions as an administrative or economic center for, a specified region.
- 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_69ca84dfde1481909f47c286d715f892 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb313134081908eb0ba3a22b22e2b |
completed | April 2, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cd03e01ea881909a7d93fc3994ace5 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:31 p.m.