Triple
T31378023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uí Ailello |
E800362
|
entity |
| Predicate | hasAncestralGroup |
P34787
|
FINISHED |
| Object | Connachta |
E1938934
|
NE 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: Connachta | Statement: [Uí Ailello, hasAncestralGroup, Connachta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralGroup Context triple: [Uí Ailello, hasAncestralGroup, Connachta]
-
A.
hasCommonAncestryGroup
Indicates that the related entities share membership in the same ancestral or lineage-based group.
-
B.
hasAncestralTo
Indicates that one entity is an ancestor of another, existing in an earlier generation within a lineage or heritage chain.
-
C.
hasAncestor
Indicates that one entity is an ancestor (direct or indirect, such as a parent, grandparent, etc.) of another entity in a genealogical or hierarchical lineage.
-
D.
hasAncestralProperty
Indicates that an entity possesses a property, trait, or characteristic that originates from or is inherited through its ancestors.
-
E.
hasAncestralRoots
chosen
Indicates that one entity originates from, descends from, or is historically rooted in another entity or place.
- F. None of above.
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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b79b537208190834afe56525a187f |
completed | June 12, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 29, 2026, 9:18 p.m.