Triple
T28845447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ji clan |
E728441
|
entity |
| Predicate | heldHereditaryPowerIn |
P165659
|
FINISHED |
| Object | State of Yan |
—
|
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 Yan | Statement: [Ji clan, heldHereditaryPowerIn, State of Yan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldHereditaryPowerIn Context triple: [Ji clan, heldHereditaryPowerIn, State of Yan]
-
A.
heldDukedomInHerOwnRight
Indicates that a person possessed and exercised the title and authority of a dukedom independently, rather than through marriage or another’s status.
-
B.
heldByHeirApparentOf
Indicates that something is possessed, controlled, or occupied by the heir apparent of a particular person, title, or position.
-
C.
heldUnderDynasty
Indicates that an entity’s position, title, or authority was exercised during the rule of a specific dynasty.
-
D.
hereditaryMonarch
Indicates that a person holds a monarchical position that is passed down through a family line according to hereditary succession rules.
-
E.
heldByDuringReignOf
Indicates that a position, title, or role was held by a person or entity specifically during the reign or rule of a particular sovereign or authority.
- F. None of above. chosen
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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659d446708190aaa57d5a1181209e |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:42 a.m.