Triple
T30119602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaochengren |
E765521
|
entity |
| Predicate | childStatusOfYunreng |
P33133
|
FINISHED |
| Object | second son of the Kangxi Emperor |
—
|
LITERAL 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: second son of the Kangxi Emperor | Statement: [Empress Xiaochengren, childStatusOfYunreng, second son of the Kangxi Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childStatusOfYunreng Context triple: [Empress Xiaochengren, childStatusOfYunreng, second son of the Kangxi Emperor]
-
A.
childStatus
chosen
Indicates the current condition, role, or state of a child entity in relation to its parent or context.
-
B.
childrenStatus
Indicates the relationship describing whether and how an entity has children, including their presence, number, or relevant child-related status.
-
C.
childName
Indicates that one entity is the name (or given name) of a child associated with another entity.
-
D.
childIs
Indicates that one entity is the child (offspring or subordinate descendant) of another entity.
-
E.
childrenWith
Indicates that two or more entities share one or more children together as parents or guardians.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f7efc3c8190986d2d95b7a23729 |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 7:13 p.m.