Triple
T36015961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of the Ming |
E1041838
|
entity |
| Predicate | typicalTitleForm |
P207135
|
FINISHED |
| Object | Temple name plus posthumous title |
—
|
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: Temple name plus posthumous title | Statement: [Emperor of the Ming, typicalTitleForm, Temple name plus posthumous title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTitleForm Context triple: [Emperor of the Ming, typicalTitleForm, Temple name plus posthumous title]
-
A.
nativeTitleForm
Indicates the form of a title as it appears in the original or native language of the entity it names.
-
B.
titleOfTitle
Indicates that one title is the title of another title (e.g., a sub-title or alternate title associated with a primary title).
-
C.
commonTitle
Indicates that two or more entities share the same title or designation.
-
D.
titleFormality
Indicates the degree of formality conveyed by a title used to address or refer to an entity.
-
E.
providedTitle
Indicates that one entity has supplied or assigned a specific title or designation to another 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_69f76e2b981881908e4e160607fa82eb |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.