Triple
T32995091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eóganacht Chaisil |
E844203
|
entity |
| Predicate | hasDynasticBase |
P159148
|
FINISHED |
| Object | Cashel region |
—
|
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: Cashel region | Statement: [Eóganacht Chaisil, hasDynasticBase, Cashel region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynasticBase Context triple: [Eóganacht Chaisil, hasDynasticBase, Cashel region]
-
A.
isDynastic
Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
-
B.
hasDynasticFunction
Indicates that something serves a role or purpose within a dynasty, such as supporting its continuity, authority, or internal organization.
-
C.
hasDynast
chosen
Indicates that an entity is associated with or ruled by a particular dynasty.
-
D.
hasDynasticCulture
Indicates that an entity belongs to or is associated with a particular dynastic cultural tradition or heritage.
-
E.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:22 a.m.