Triple
T31209744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dál gCais in Munster kingship |
E795702
|
entity |
| Predicate | hasMainDynasty |
P25072
|
FINISHED |
| Object | Dál gCais |
—
|
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 gCais | Statement: [Dál gCais in Munster kingship, hasMainDynasty, Dál gCais]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainDynasty Context triple: [Dál gCais in Munster kingship, hasMainDynasty, Dál gCais]
-
A.
hasMajorDynasty
chosen
Indicates that an entity (such as a region, state, or historical period) is associated with or ruled by a particular major dynasty.
-
B.
hasDynastyFounded
Indicates that an entity is the founder or originator of a particular dynasty.
-
C.
hasCurrentDynasty
Indicates that an entity is currently ruled, governed, or controlled by the specified dynasty.
-
D.
hasLastDynasty
Indicates that an entity’s most recent or final ruling dynasty is the specified dynasty.
-
E.
hasCapitalInDynasty
Indicates that a particular city or location served as the capital during a specified dynasty or historical ruling 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0004582bb08190b8d0b88251e8d333 |
completed | May 10, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a0003e3e5588190933beea5fb28f150 |
completed | May 10, 2026, 4:04 a.m. |
Created at: April 29, 2026, 9:09 p.m.