Triple
T30192192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empress Xiaozhaoren |
E767520
|
entity |
| Predicate | maternalGrandfatherPosition |
P86433
|
FINISHED |
| Object | Grand Secretary |
—
|
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: Grand Secretary | Statement: [Empress Xiaozhaoren, maternalGrandfatherPosition, Grand Secretary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maternalGrandfatherPosition Context triple: [Empress Xiaozhaoren, maternalGrandfatherPosition, Grand Secretary]
-
A.
maternalGrandfatherOf
Indicates that one person is the father of another person's mother.
-
B.
maternalGrandfatherInstanceOf
chosen
Indicates that an entity is an instance of the class or role of a maternal grandfather (the father of one’s mother).
-
C.
maternalGrandsonOf
Indicates that one entity is the male child of the daughter of another entity (i.e., the other entity’s grandson through their maternal line).
-
D.
maternalGreatGrandfather
Indicates that one entity is the father of the mother of another entity’s mother (i.e., the person’s maternal great-grandfather).
-
E.
paternal grandmother
Indicates that one entity is the mother of the other entity’s father.
- 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_69f2247db1108190835c0727c97637c3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 7:29 p.m.