Triple
T10659459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Múscraí Gaeltacht |
E251184
|
entity |
| Predicate | dialectPreserved |
P28812
|
FINISHED |
| Object | Munster Irish dialect |
—
|
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: Munster Irish dialect | Statement: [Múscraí Gaeltacht, dialectPreserved, Munster Irish dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dialectPreserved Context triple: [Múscraí Gaeltacht, dialectPreserved, Munster Irish dialect]
-
A.
regionalDialect
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
notableDialect
Indicates that an entity is recognized for having a distinct or noteworthy dialect associated with it.
-
C.
historicalDialect
Indicates that one dialect is a historically earlier or ancestral form of another dialect.
-
D.
hasTraditionalDialect
chosen
Indicates that an entity possesses or is associated with a traditional form or variety of a language or dialect.
-
E.
majorDialectOf
Indicates that one dialect is the primary or most prominent dialect associated with a particular language or 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6e0174dc4819093e577993c65ed32 |
completed | April 8, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:07 p.m.