Triple

T38055384
Position Surface form Disambiguated ID Type / Status
Subject Parliament of 1626 E949884 entity
Predicate associatedMonarchDynasty P21467 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: [Parliament of 1626, associatedMonarchDynasty, House of Stuart]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedMonarchDynasty
Context triple: [Parliament of 1626, associatedMonarchDynasty, House of Stuart]
  • A. regentDynasty
    Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
  • B. associatedWithMonarch chosen
    Indicates a relationship where an entity has a connection or affiliation with a monarch, such as through service, governance, lineage, or formal association.
  • C. monarchInFamily
    Indicates that a member of a family holds (or held) the position of monarch within that family lineage.
  • D. associatedWithMonarchy
    Indicates a relationship in which something has a connection, link, or relevance to a monarchy or monarchical system.
  • E. associatedWithDynasty
    Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
  • 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_69f76f000cf081908c11fb5443b392e6 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a037df1223c8190a5d61e4f8e6fd613 completed May 12, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_6a415d356f7881909dbdc4ee8fff1e58 completed June 28, 2026, 5:43 p.m.
PD Predicate disambiguation batch_6a037a1ad6c48190bfe35d350c1b4751 completed May 12, 2026, 7:06 p.m.
Created at: May 3, 2026, 4:21 p.m.