Triple
T30954992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kincora |
E788650
|
entity |
| Predicate | dynasticSeatOf |
P42447
|
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: [Kincora, dynasticSeatOf, Dál gCais]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticSeatOf Context triple: [Kincora, dynasticSeatOf, Dál gCais]
-
A.
dynasticSeat
chosen
Indicates that a particular location serves as the principal seat of power or ruling center for a specific dynasty or ruling family.
-
B.
ancestralSeatOf
Indicates that one entity is the traditional or original home, origin place, or foundational location associated with the lineage, heritage, or authority of another entity.
-
C.
usedAsSeatOfPowerBy
Indicates that something serves as the primary location or base from which an individual or group exercises authority, control, or governance.
-
D.
associatedDynastyCapital
Indicates a relationship where a dynasty is linked to the city that served as its capital.
-
E.
isDiplomaticCenterOf
Indicates that a location serves as the primary site or hub for conducting diplomatic activities and relations for a specified entity.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:53 p.m.