Triple
T22247752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukedom of Atholl |
E549888
|
entity |
| Predicate | hereditaryChiefOf |
P31750
|
FINISHED |
| Object | Clan Murray |
—
|
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: Clan Murray | Statement: [Dukedom of Atholl, hereditaryChiefOf, Clan Murray]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryChiefOf Context triple: [Dukedom of Atholl, hereditaryChiefOf, Clan Murray]
-
A.
hasHereditaryChief
chosen
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
B.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
-
C.
headOfNobleFamily
Indicates that one entity holds the position of leader or chief authority over a particular noble family.
-
D.
nobleTitleHeirTo
Indicates that one entity is the designated heir to the noble title held by another entity.
-
E.
hereditaryTitleFor
Indicates that one entity is a hereditary title that is held by, or associated with, another entity, typically passed down through a family line.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f13219dc3481908dd987c4e98623e6 |
completed | April 28, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:38 p.m.