Triple
T36165925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mag Uidhir |
E1045996
|
entity |
| Predicate | linkedClanRole |
P134359
|
FINISHED |
| Object | ruling dynasty in Fermanagh |
—
|
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: ruling dynasty in Fermanagh | Statement: [Mag Uidhir, linkedClanRole, ruling dynasty in Fermanagh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedClanRole Context triple: [Mag Uidhir, linkedClanRole, ruling dynasty in Fermanagh]
-
A.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
B.
associatedClanChief
Indicates a relationship where an entity is linked or connected to a particular clan chief, typically as the chief responsible for or representing that entity.
-
C.
clanAssociationType
chosen
Indicates the specific nature or role of an entity’s association or membership within a clan.
-
D.
clanSeatRelation
Indicates a relationship where a clan holds, occupies, or is associated with a particular seat, position, or place of authority.
-
E.
clanSystem
Indicates a social structure in which individuals are organized into kin-based groups (clans) that define relationships, obligations, and affiliations among them.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 3, 2026, 4:08 p.m.