Triple
T29800225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Margaret Bellenden |
E756671
|
entity |
| Predicate | supportsDynasty |
P157636
|
FINISHED |
| Object | House of Stuart |
E3494
|
NE 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: House of Stuart | Statement: [Lady Margaret Bellenden, supportsDynasty, House of Stuart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDynasty Context triple: [Lady Margaret Bellenden, supportsDynasty, House of Stuart]
-
A.
basedOnDynasty
Indicates that something is derived from, influenced by, or established on the foundation of a particular dynasty.
-
B.
possibleDynasty
Indicates that one entity could plausibly be the ruling dynasty associated with, or historically linked to, another entity.
-
C.
dynasticLegacy
Indicates that a lineage, tradition, or influence is passed down through successive generations within a dynasty or family line.
-
D.
dynastyProvided
chosen
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
-
E.
isDynastic
Indicates that a relationship, status, or succession is based on or belongs to a hereditary ruling family or lineage.
- F. None of above.
Provenance (4 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26c8d8f2808190b41eaa9824f6525c |
completed | June 8, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:17 p.m.