Triple
T2933951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jianwen Emperor |
E79220
|
entity |
| Predicate | reignCharacteristics |
P10867
|
FINISHED |
| Object | short reign |
—
|
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: short reign | Statement: [Jianwen Emperor, reignCharacteristics, short reign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignCharacteristics Context triple: [Jianwen Emperor, reignCharacteristics, short reign]
-
A.
reignCharacterizedBy
chosen
Indicates that a ruler’s period of governance is defined or distinguished by a particular quality, condition, or notable feature.
-
B.
describesReignOf
Indicates that something (such as a text, record, or account) provides information about the period during which a particular ruler or authority was in power.
-
C.
historicalCharacteristic
Indicates that an entity possesses a trait, feature, or quality that is rooted in or defined by its history or past events.
-
D.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
E.
capitalDuringReign
Indicates that a particular city or location served as the capital of a political entity during the reign of a specified ruler.
- 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_69ad8b0fbab081908f6a61567c045d8d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad983b65f881909b8b7d3dc5c224fd |
completed | March 8, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9606e8348190bb19df33a2709674 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:56 p.m.