Triple

T27887488
Position Surface form Disambiguated ID Type / Status
Subject Han clan E705269 entity
Predicate wasRulingHouseOf P9023 FINISHED
Object State of Han 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: State of Han | Statement: [Han clan, wasRulingHouseOf, State of Han]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wasRulingHouseOf
Context triple: [Han clan, wasRulingHouseOf, State of Han]
  • A. rulingHouse chosen
    Indicates that one entity serves as the dynastic or noble family that holds ruling authority over another entity, such as a state, territory, or polity.
  • B. formerRulerHouse
    Indicates that a person once ruled on behalf of, or as a member of, a particular ruling house or dynasty but no longer holds that ruling position.
  • C. monarchicalHouse
    Indicates that an entity belongs to, is associated with, or is part of a particular royal or monarchical house or dynasty.
  • D. dynasticHouseInvolved
    Indicates that a particular dynastic house (royal or noble lineage) is involved in, associated with, or plays a role in the referenced event, entity, or relationship.
  • E. crownedMonarchHouse
    Indicates that a particular royal house is the one from which a given monarch was crowned or to which that crowned monarch belongs.
  • 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_69ef96b39c448190a9b3aa6672a5168f completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f639b25b2c819090f30ea43ffae5ad completed May 2, 2026, 5:51 p.m.
PD Predicate disambiguation batch_69f6318be69481909d1bcf29b7b60eb2 completed May 2, 2026, 5:17 p.m.
Created at: April 27, 2026, 6:34 p.m.