Triple
T29256178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Houzhu |
E741709
|
entity |
| Predicate | appliedToTitleHolder |
P193414
|
FINISHED |
| Object | last emperor of Shu Han |
—
|
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: last emperor of Shu Han | Statement: [Houzhu, appliedToTitleHolder, last emperor of Shu Han]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToTitleHolder Context triple: [Houzhu, appliedToTitleHolder, last emperor of Shu Han]
-
A.
appliedToTitle
Indicates that something (such as a rule, action, or attribute) is applied specifically to a given title.
-
B.
refersToTitleHolder
Indicates that one entity makes reference to, or designates, the entity that currently holds a specific title or position.
-
C.
hasTitleHolder
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
D.
includedTitleHolder
Indicates that an entity is recognized or recorded as holding a specified title within a given context or collection.
-
E.
affectedTitleHolder
Indicates that a title holder is impacted or influenced in some way by a specified event, action, or relationship.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: April 28, 2026, 12:37 p.m.