Triple
T29493492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhao Hongyin |
E748148
|
entity |
| Predicate | dynastyAffiliation |
P7426
|
FINISHED |
| Object | Later Zhou dynasty |
—
|
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: Later Zhou dynasty | Statement: [Zhao Hongyin, dynastyAffiliation, Later Zhou dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyAffiliation Context triple: [Zhao Hongyin, dynastyAffiliation, Later Zhou dynasty]
-
A.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
B.
associatedWithDynasty
chosen
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
C.
dynastyInvolved
Indicates that a particular dynasty participates in, is associated with, or plays a role in the referenced event, process, or situation.
-
D.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
E.
dynastyProvided
Indicates that a particular dynasty supplied, supported, or was responsible for providing something to another entity or context.
- 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_69f0bd448c6881908aa6b475cefd5ddc |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 4:16 p.m.