Triple
T24463844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cenél nÓengusa |
E616909
|
entity |
| Predicate | overkingdomContext |
P106028
|
FINISHED |
| Object | Dál Riata |
—
|
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: Dál Riata | Statement: [Cenél nÓengusa, overkingdomContext, Dál Riata]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overkingdomContext Context triple: [Cenél nÓengusa, overkingdomContext, Dál Riata]
-
A.
kingdom
Indicates that an entity is classified within a particular biological kingdom in a taxonomic hierarchy.
-
B.
clientKingdomOf
chosen
Indicates a relationship where one kingdom is politically subordinate or tributary to another, more powerful kingdom while retaining limited internal autonomy.
-
C.
hadKingdom
Indicates that an entity possessed or ruled over a particular kingdom.
-
D.
mentionsKingdom
Indicates that one entity explicitly refers to or brings up the topic of a kingdom in relation to another entity.
-
E.
wasKingdom
Indicates that one entity functioned as the sovereign kingdom or ruling polity of another entity during a particular period.
- 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_69e2d7ef9fe08190a0613908758b4e86 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298cc60448190a5383d452f563834 |
completed | April 29, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:19 a.m.