Triple
T28047099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuande |
E708713
|
entity |
| Predicate | bearerPersonalName |
P165729
|
FINISHED |
| Object | Liu Bei |
—
|
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 Bei | Statement: [Xuande, bearerPersonalName, Liu Bei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerPersonalName Context triple: [Xuande, bearerPersonalName, Liu Bei]
-
A.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by another entity.
-
B.
notableBearerFullName
Indicates that a full personal name is that of a notable or well-known bearer associated with the referenced entity.
-
C.
bearerByname
Indicates that an entity is known or referred to by a particular byname or secondary name.
-
D.
bearerAnglicizedNameOf
Indicates that one entity is the anglicized (English-adapted) version of the name borne by another entity.
-
E.
hasSurnameBearer
Indicates that a particular surname is borne or carried by a specific person or entity.
- 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_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 27, 2026, 8:30 p.m.