Triple
T3592183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiajing Emperor |
E76049
|
entity |
| Predicate | regnalOrder |
P49591
|
FINISHED |
| Object | 11th emperor of the Ming dynasty |
—
|
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: 11th emperor of the Ming dynasty | Statement: [Jiajing Emperor, regnalOrder, 11th emperor of the Ming dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regnalOrder Context triple: [Jiajing Emperor, regnalOrder, 11th emperor of the Ming dynasty]
-
A.
orderRegardedAs
Indicates that one order is considered or treated as equivalent to, or in the same category as, another order within a given context or system.
-
B.
orderAuthority
Indicates that one entity has the formal power or right to issue orders or directives to another entity.
-
C.
orderGroup
Indicates that multiple individual orders are associated together as a single grouped order entity or batch.
-
D.
orderType
Indicates the specific category or classification of an order, such as its purpose, channel, or processing method.
-
E.
orderFoundedBy
Indicates that a particular order or organization was established or created by a specific person or 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_69ad85d8042081908af94a04c410dec0 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc15a546481909c72dac80d65e1fb |
completed | March 8, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:22 p.m.