Triple
T28335060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liu Ruyi |
E717646
|
entity |
| Predicate | statusInSuccession |
P189428
|
FINISHED |
| Object | potential heir apparent |
—
|
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: potential heir apparent | Statement: [Liu Ruyi, statusInSuccession, potential heir apparent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInSuccession Context triple: [Liu Ruyi, statusInSuccession, potential heir apparent]
-
A.
supportedSuccessionOf
Indicates that one entity actively endorsed or helped bring about the transfer of power, position, or role from a predecessor to a successor.
-
B.
successionLawStatus
Indicates the legal status or condition governing how succession or inheritance is determined or applied.
-
C.
statusAfterSupersession
Indicates the status or condition an entity holds after it has been superseded by another entity.
-
D.
hasSuccession
Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
-
E.
successorStatusAtAccession
Indicates the status or position held by a successor at the time they formally assumed their role or office.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: April 28, 2026, 12:35 a.m.