Triple
T9272829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uí Briúin |
E222871
|
entity |
| Predicate | hadBranches |
P49773
|
FINISHED |
| Object | royal lineages in Aí |
—
|
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: royal lineages in Aí | Statement: [Uí Briúin, hadBranches, royal lineages in Aí]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBranches Context triple: [Uí Briúin, hadBranches, royal lineages in Aí]
-
A.
hadBranchIn
Indicates that an organization or entity maintained a branch, office, or subsidiary located in another specified place or entity.
-
B.
hasTwoBranches
Indicates that the related entity is divided into or composed of exactly two distinct branches.
-
C.
hasFamilyBranch
chosen
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
D.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
-
E.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another 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_69ca841ffe208190aa7bcffbef2f8379 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0787d2e48190ad56cf3abf12d409 |
completed | April 1, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.