Triple
T31210129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterford County Council |
E795714
|
entity |
| Predicate | languageAreaIncluded |
P53840
|
FINISHED |
| Object | Gaeltacht |
—
|
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: Gaeltacht | Statement: [Waterford County Council, languageAreaIncluded, Gaeltacht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageAreaIncluded Context triple: [Waterford County Council, languageAreaIncluded, Gaeltacht]
-
A.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
B.
alsoInLanguageRegion
chosen
Indicates that two or more entities are located within or associated with the same language-defined geographic region.
-
C.
primaryLanguageArea
Indicates that a specified region or area is one where a particular language is predominantly used or officially recognized as primary.
-
D.
regionOfMajorLanguage
Indicates the geographic region where a particular language is predominantly spoken or holds major usage.
-
E.
languageFamilyCoverage
Indicates the extent to which a given entity (such as a resource, model, or system) supports or covers the languages within a specified language family.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: April 29, 2026, 9:09 p.m.