Triple
T27144276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Áras an Chontae, Castlebar |
E681899
|
entity |
| Predicate | heritageLanguageName |
P21030
|
FINISHED |
| Object | Áras an Chontae |
—
|
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: Áras an Chontae | Statement: [Áras an Chontae, Castlebar, heritageLanguageName, Áras an Chontae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageLanguageName Context triple: [Áras an Chontae, Castlebar, heritageLanguageName, Áras an Chontae]
-
A.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
-
B.
languageOfHistoricName
Indicates the language in which a historic or former name of an entity is expressed.
-
C.
hasLinguisticHeritage
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
-
D.
traditionalLanguageName
chosen
Indicates the name traditionally used in a particular language to refer to the subject entity.
-
E.
historicalLanguageOfBearers
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 27, 2026, 9:10 a.m.