Triple
T32997841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lough Veagh |
E844276
|
entity |
| Predicate | languageRegionNearby |
P29819
|
FINISHED |
| Object | Irish-speaking communities |
—
|
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-speaking communities | Statement: [Lough Veagh, languageRegionNearby, Irish-speaking communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageRegionNearby Context triple: [Lough Veagh, languageRegionNearby, Irish-speaking communities]
-
A.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
-
B.
operatorLanguageRegion
Indicates the geographic region or locale in which an operator’s language is used or applicable.
-
C.
languageOfSurroundingCountry
Indicates that a language is the primary or commonly used language in the country surrounding a given place or region.
-
D.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
-
E.
languageArea
chosen
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
Created at: May 1, 2026, 1:22 a.m.