Triple
T30927170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaeltacht |
E787888
|
entity |
| Predicate | mainChallenge |
P31731
|
FINISHED |
| Object | language shift to English |
—
|
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: language shift to English | Statement: [Gaeltacht, mainChallenge, language shift to English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainChallenge Context triple: [Gaeltacht, mainChallenge, language shift to English]
-
A.
challengeType
chosen
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
B.
relatedChallenge
Indicates that one challenge is connected to another challenge, such as being similar, dependent, or otherwise contextually linked.
-
C.
featuredChallengeCup
Indicates that a particular Challenge Cup is highlighted or given special prominence relative to others.
-
D.
hasChallenge
Indicates that an entity faces, experiences, or is confronted with a particular difficulty, obstacle, or problem.
-
E.
programChallenge
Indicates that an entity sets or presents a programming-related task or problem for another entity to solve or complete.
- 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_69f224bfaca88190b9d0dfcc86297fe9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 29, 2026, 8:51 p.m.