Triple
T34740127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caisleán an Bharraigh |
E1001471
|
entity |
| Predicate | isSpokenLanguageForm |
P17843
|
FINISHED |
| Object | Irish language |
—
|
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: Irish language | Statement: [Caisleán an Bharraigh, isSpokenLanguageForm, Irish language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSpokenLanguageForm Context triple: [Caisleán an Bharraigh, isSpokenLanguageForm, Irish language]
-
A.
isSpokenLanguage
Indicates that a language is used primarily for oral communication by speakers, as opposed to being only written or symbolic.
-
B.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
C.
isSpokenAs
chosen
Indicates that one entity is used as the spoken or verbal form of another entity (e.g., a word, name, or phrase).
-
D.
hasSpokenFormOnly
Indicates that the entity exists or is recognized only in spoken form and has no corresponding written representation.
-
E.
usedInSpokenForm
Indicates that something (such as a word, name, or expression) is employed in spoken language or oral communication.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.