Triple
T28047119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuande |
E708713
|
entity |
| Predicate | bearerChild |
P169577
|
FINISHED |
| Object | Liu Shan |
—
|
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: Liu Shan | Statement: [Xuande, bearerChild, Liu Shan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerChild Context triple: [Xuande, bearerChild, Liu Shan]
-
A.
bearerSibling
Indicates that the related entity is a sibling (sharing at least one parent) of the bearer entity.
-
B.
bearer
Indicates that one entity carries, holds, or possesses another entity, often as the current holder of a right, document, or object.
-
C.
bearerSuccessor
Indicates that one bearer entity succeeds or follows another in holding a particular role, title, or responsibility.
-
D.
bearerPredecessor
Indicates that one entity previously held a role, title, or position that is now held by another entity, establishing a predecessor-successor relationship between them.
-
E.
bearerFounded
Indicates that the bearer (such as a person or organization) is the one who established or created the associated entity (such as a company, institution, or project).
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 27, 2026, 8:30 p.m.