Triple
T29203598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaozu |
E740347
|
entity |
| Predicate | honorificForRegime |
P174285
|
FINISHED |
| Object | Cao Wei |
—
|
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: Cao Wei | Statement: [Gaozu, honorificForRegime, Cao Wei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificForRegime Context triple: [Gaozu, honorificForRegime, Cao Wei]
-
A.
honorificForRegion
Indicates that a particular honorific title or form of address is specifically used for, or associated with, a given geographic region.
-
B.
hasHonorificSystem
Indicates that a language or culture employs a structured system of honorifics to mark social status, respect, or formality in communication.
-
C.
honorificType
Indicates the type or category of honorific or formal title associated with an entity in a given context.
-
D.
honorificOrigin
Indicates that an honorific title or form of address originates from, or is derived from, a particular source, culture, language, or context.
-
E.
honorificForEthnicityContext
Indicates that an honorific or respectful form of address is used specifically in relation to a person’s ethnicity or ethnic background.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 28, 2026, 12:08 p.m.