Triple
T36029961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campaign to Pacify the Difficulties |
E1042231
|
entity |
| Predicate | hasIncumbentRuler |
P202550
|
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, hasIncumbentRuler, Jianwen Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIncumbentRuler Context triple: [Campaign to Pacify the Difficulties, hasIncumbentRuler, Jianwen Emperor]
-
A.
hasFormerRuler
Indicates that an entity previously served as the ruler of another entity but no longer holds that ruling position.
-
B.
lastDeJureHolder
Indicates that one entity is the most recent legally recognized holder or possessor of another entity (such as a title, office, or right).
-
C.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
-
D.
hasRulingPeople
Indicates that a group or entity serves as the governing or ruling authority over another entity.
-
E.
hasFamousRuler
Indicates that an entity is or was ruled by a ruler who is widely recognized or historically notable.
- 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_69f76e2c568881909e1e21f85252b0f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_6a008eba6de8819083165152448f6071 |
completed | May 10, 2026, 1:57 p.m. |
Created at: May 3, 2026, 4:07 p.m.