Triple
T29256168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houzhu |
E741709
|
entity |
| Predicate | appliedToPersonBirthName |
P18679
|
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: [Houzhu, appliedToPersonBirthName, Liu Shan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToPersonBirthName Context triple: [Houzhu, appliedToPersonBirthName, Liu Shan]
-
A.
appliesToPersonBirthName
chosen
Indicates that the referenced value is used as the birth name of the specified person.
-
B.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by another entity.
-
C.
appliedToPersonBornIn
Indicates that something (such as a rule, action, status, or condition) is applied specifically to a person who was born in a particular place.
-
D.
namedAfterDateOfBirth
Indicates that something (such as a person, event, or entity) is named after a specific date corresponding to a birth.
-
E.
authorBirthName
Indicates the full personal name an author was given at birth, before any later name changes or pseudonyms.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 28, 2026, 12:37 p.m.