Triple
T33156879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fiachrae mac Eochaid Mugmedón |
E848602
|
entity |
| Predicate | nameMeaningRelation |
P176144
|
FINISHED |
| Object | gives name to Uí Fiachrach |
—
|
LITERAL FINISHED |
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: gives name to Uí Fiachrach | Statement: [Fiachrae mac Eochaid Mugmedón, nameMeaningRelation, gives name to Uí Fiachrach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameMeaningRelation Context triple: [Fiachrae mac Eochaid Mugmedón, nameMeaningRelation, gives name to Uí Fiachrach]
-
A.
hasNameMeaningRelation
Indicates that there is a relationship between an entity and a name that conveys or encodes a particular meaning or significance.
-
B.
birthNameMeaning
Indicates the semantic meaning or significance associated with a person's birth name.
-
C.
nameMeaningCertainty
Indicates how certain or confident a source is about the correctness or validity of an entity’s name meaning.
-
D.
pairNameMeaning
Indicates that the relationship specifies the semantic meaning or significance associated with a particular pair name.
-
E.
currentNameMeaning
Indicates that the predicate expresses the meaning or significance of an entity’s current name.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:28 a.m.