Triple
T31784256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drummond of Strathallan |
E811284
|
entity |
| Predicate | hereditaryTitleType |
P170048
|
FINISHED |
| Object | viscountcy |
—
|
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: viscountcy | Statement: [Drummond of Strathallan, hereditaryTitleType, viscountcy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hereditaryTitleType Context triple: [Drummond of Strathallan, hereditaryTitleType, viscountcy]
-
A.
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.
-
B.
hereditaryTitleInheritance
Indicates that a hereditary title is passed from one individual to another according to established rules of succession.
-
C.
nobilityTitleType
chosen
Indicates the specific kind or category of noble rank or title associated with an entity.
-
D.
nobleTitleHeirTo
Indicates that one entity is the designated heir to the noble title held by another entity.
-
E.
hereditaryPeerage
Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe760f88190b01131bf42e4066c |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:37 p.m.