Triple
T33037260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eóganacht Glendamnach |
E845350
|
entity |
| Predicate | hasRivalBranch |
P151485
|
FINISHED |
| Object | Eóganacht Raithlind |
—
|
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: Eóganacht Raithlind | Statement: [Eóganacht Glendamnach, hasRivalBranch, Eóganacht Raithlind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalBranch Context triple: [Eóganacht Glendamnach, hasRivalBranch, Eóganacht Raithlind]
-
A.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
B.
hasCollateralBranch
chosen
Indicates that one entity possesses or is associated with a secondary or side branch related to another entity.
-
C.
mayHaveBranch
Indicates that an entity is permitted or able to possess one or more branches as part of its structure or organization.
-
D.
hasTwoBranches
Indicates that the related entity is divided into or composed of exactly two distinct branches.
-
E.
hasBranchOffice
Indicates that one organization maintains a branch office or subsidiary location in another place or entity.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:24 a.m.