Triple
T30590728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changli Xiansheng |
E778645
|
entity |
| Predicate | bearerStyleName |
P144572
|
FINISHED |
| Object | Tuizhi |
—
|
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: Tuizhi | Statement: [Changli Xiansheng, bearerStyleName, Tuizhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerStyleName Context triple: [Changli Xiansheng, bearerStyleName, Tuizhi]
-
A.
bearerStyleCharacteristic
Indicates that a bearer (such as a person or object) exhibits or is associated with a particular style-related characteristic.
-
B.
nameStyle
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
-
C.
bearerTitle
Indicates that one entity holds or is designated by a specific formal title associated with a role, rank, or position.
-
D.
bearerStageName
chosen
Indicates that an entity is known or performs under a particular stage name.
-
E.
bindingStyle
Indicates the method or format by which two components, systems, or interfaces are connected or integrated for interaction.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 29, 2026, 8:24 p.m.