Triple
T36029979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campaign to Pacify the Difficulties |
E1042231
|
entity |
| Predicate | involvesEmperor |
P27872
|
FINISHED |
| Object | Jianwen Emperor |
—
|
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: Jianwen Emperor | Statement: [Campaign to Pacify the Difficulties, involvesEmperor, Jianwen Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesEmperor Context triple: [Campaign to Pacify the Difficulties, involvesEmperor, Jianwen Emperor]
-
A.
emperorAction
Indicates actions performed by, initiated by, or under the direct authority of an emperor.
-
B.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
C.
associatedWithEmperor
chosen
Indicates a relationship in which an entity has a connection, link, or affiliation with an emperor, such as through service, influence, kinship, or shared authority.
-
D.
coEmperorWith
Indicates that two individuals simultaneously share the position and authority of emperor within the same imperial system.
-
E.
concludedUnderEmperor
Indicates that an event, agreement, or process was completed or formally concluded during the reign of a specific emperor.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 3, 2026, 4:07 p.m.