Triple
T29818677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giric mac Dúngail |
E757183
|
entity |
| Predicate | possibleJointRulerWith |
P20514
|
FINISHED |
| Object | Eochaid |
—
|
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: Eochaid | Statement: [Giric mac Dúngail, possibleJointRulerWith, Eochaid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleJointRulerWith Context triple: [Giric mac Dúngail, possibleJointRulerWith, Eochaid]
-
A.
possiblyRuledAs
Indicates that one entity may have exercised governance or authority over another, but this ruling is uncertain or not definitively established.
-
B.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
C.
partnerInRuleWith
chosen
Indicates that two or more entities jointly participate as partners in establishing, enforcing, or being governed by the same rule or regulatory framework.
-
D.
providedRulerFor
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
-
E.
jointAuthorityOf
Indicates that two or more entities share formal power or control over a decision, resource, or domain.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 5:27 p.m.