Triple
T31130475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ráth Chairn |
E793488
|
entity |
| Predicate | purposeOfResettlement |
P171617
|
FINISHED |
| Object | promotion of 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: promotion of Irish language | Statement: [Ráth Chairn, purposeOfResettlement, promotion of Irish language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfResettlement Context triple: [Ráth Chairn, purposeOfResettlement, promotion of Irish language]
-
A.
resettledBy
Indicates that an entity has been moved or established anew in a location or context by another agent or authority.
-
B.
resettlementStatus
Indicates the current stage or condition of an entity’s relocation or re-establishment process in a new place.
-
C.
resettlementIssue
Indicates a relationship where an entity faces problems, challenges, or complications related to being resettled or relocated.
-
D.
resettlementStart
Indicates the point in time when a process of relocating people or communities to a new place begins.
-
E.
majorResettlementArea
Indicates that a location serves as a primary or significant destination area where people are being resettled.
- F. None of above. chosen
Provenance (4 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:05 p.m.