Triple
T13304502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacDonald of Keppoch |
E316901
|
entity |
| Predicate | chieflyLine |
P97526
|
FINISHED |
| Object | descendants of Ranald Mòr |
—
|
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: descendants of Ranald Mòr | Statement: [Clan MacDonald of Keppoch, chieflyLine, descendants of Ranald Mòr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chieflyLine Context triple: [Clan MacDonald of Keppoch, chieflyLine, descendants of Ranald Mòr]
-
A.
mainLine
Indicates that something serves as the primary or central line, route, or sequence among a set of related lines.
-
B.
rulingLine
chosen
Indicates that one entity is the ruling or governing lineage, dynasty, or family over another entity (such as a territory, people, or polity).
-
C.
keyLine
Indicates that a line or segment serves as a primary or defining reference line within a structure, system, or representation.
-
D.
formerLine
Indicates that an entity previously served as a particular transit or service line but no longer does so.
-
E.
isMajorLineOf
Indicates that one entity is a primary or principal route, branch, or component within the structure or network represented by the other 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_69d806b40ab4819094adf6c374f4811a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:28 p.m.