Triple
T31209889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crúachan |
E795706
|
entity |
| Predicate | governingMythicDynasty |
P200963
|
FINISHED |
| Object | kings of Connacht |
—
|
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: kings of Connacht | Statement: [Crúachan, governingMythicDynasty, kings of Connacht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingMythicDynasty Context triple: [Crúachan, governingMythicDynasty, kings of Connacht]
-
A.
mythologicalCapital
Indicates that a location serves as the principal or central city associated with a particular mythology or pantheon.
-
B.
honorsDynasty
Indicates that one entity pays tribute or shows respect and recognition to a particular dynasty.
-
C.
mythicAction
Indicates an action or event characterized by legendary, supernatural, or culturally mythologized qualities within a narrative or symbolic context.
-
D.
mythicAlliance
Indicates a cooperative or strategic partnership formed between entities within a legendary, mythical, or supernatural context.
-
E.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
- F. None of above. chosen
Provenance (4 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_69ffbe9e47688190a2692566dc326646 |
completed | May 9, 2026, 11:09 p.m. |
| PD | Predicate disambiguation | batch_69ffbb7b45388190b62cbde5c2d435cd |
completed | May 9, 2026, 10:55 p.m. |
| PDg | Predicate description generation | batch_69ffbe9c7c348190b6b72455d6a3e3d8 |
completed | May 9, 2026, 11:09 p.m. |
Created at: April 29, 2026, 9:09 p.m.