Triple
T27766591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sima clan |
E701615
|
entity |
| Predicate | dynasticHouseName |
P131768
|
FINISHED |
| Object | House of Sima |
—
|
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: House of Sima | Statement: [Sima clan, dynasticHouseName, House of Sima]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticHouseName Context triple: [Sima clan, dynasticHouseName, House of Sima]
-
A.
dynasticSurname
Indicates that the two entities share a family name associated with a particular dynasty or ruling lineage.
-
B.
titleHolderDynasticHouse
Indicates the dynastic house or ruling family that holds a particular title.
-
C.
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.
-
D.
monarchicalHouse
chosen
Indicates that an entity belongs to, is associated with, or is part of a particular royal or monarchical house or dynasty.
-
E.
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).
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:31 p.m.