Triple
T9273528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Official Languages Act 2003 |
E222887
|
entity |
| Predicate | languageConcerned |
P69046
|
FINISHED |
| Object | Irish language |
—
|
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 language | Statement: [Official Languages Act 2003, languageConcerned, Irish language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageConcerned Context triple: [Official Languages Act 2003, languageConcerned, Irish language]
-
A.
primaryLanguageConcerned
Indicates that the relationship or action specifically involves or pertains to the main or principal language in question.
-
B.
languageDiscussedIn
chosen
Indicates that a particular language is the topic of discussion within a specified context, source, or discourse.
-
C.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
-
D.
languageFamilyConcerned
Indicates that something is related to, involves, or pertains to a particular language family.
-
E.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
- 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0788e87c81909ccda40d94cc6705 |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.