Triple
T31048383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cenél Conaill |
E791189
|
entity |
| Predicate | producedHighKingsOf |
P91909
|
FINISHED |
| Object | Tara |
—
|
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: Tara | Statement: [Cenél Conaill, producedHighKingsOf, Tara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedHighKingsOf Context triple: [Cenél Conaill, producedHighKingsOf, Tara]
-
A.
producedMonarchsOf
Indicates that one entity created, generated, or was responsible for bringing into existence the monarchs associated with another entity.
-
B.
mostPowerfulKing
Indicates that the subject is the king who holds the greatest power or authority among a specified group of kings.
-
C.
producedRulingDynastyOf
chosen
Indicates that one entity (such as a region, people, or prior polity) gave rise to or was the origin context for a particular ruling dynasty.
-
D.
producedEmperor
Indicates that one entity brought about, created, or was responsible for the rise or existence of an emperor.
-
E.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 29, 2026, 9 p.m.