Triple
T38662139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianming |
E940361
|
entity |
| Predicate | precedesInDynasticHistory |
P155647
|
FINISHED |
| Object | Qing dynasty |
—
|
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: Qing dynasty | Statement: [Tianming, precedesInDynasticHistory, Qing dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesInDynasticHistory Context triple: [Tianming, precedesInDynasticHistory, Qing dynasty]
-
A.
historicalEntityPredecessor
Indicates that one historical entity existed or held a role before another, serving as its predecessor in time or sequence.
-
B.
precedesInReign
Indicates that one ruler’s period of reign occurred entirely before another ruler’s period of reign in a temporal succession.
-
C.
predecessorInDynasticLine
Indicates that one entity held a dynastic position or title before another in the same hereditary succession line.
-
D.
predecessorDynasticSituation
chosen
Indicates that one dynastic situation directly precedes another in a historical or genealogical sequence.
-
E.
reignPreceded
Indicates that one entity’s reign occurred immediately before another entity’s reign in a temporal succession.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:33 p.m.