Triple
T28455608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crichton-Stuart |
E716702
|
entity |
| Predicate | hasHereditaryHead |
P31750
|
FINISHED |
| Object | Marquess of Bute |
—
|
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: Marquess of Bute | Statement: [Crichton-Stuart, hasHereditaryHead, Marquess of Bute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryHead Context triple: [Crichton-Stuart, hasHereditaryHead, Marquess of Bute]
-
A.
hasHereditaryBasis
Indicates that a trait, condition, or characteristic is determined or influenced by genetic inheritance passed down through family lines.
-
B.
hasHereditaryChief
chosen
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
C.
hasHereditaryNumber
Indicates that an entity is associated with a specific hereditary identifier or sequence number passed down through a lineage or inheritance chain.
-
D.
hereditaryInFamily
Indicates that a trait, condition, or characteristic is passed down through generations within the same family.
-
E.
oftenHereditary
Indicates that the relationship or property typically passes from parents to offspring through genetic inheritance.
- 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_69efd6b76f8c8190a7ba908aca280942 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 1:54 a.m.