Triple
T10028625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongzheng |
E204794
|
entity |
| Predicate | usedInChronologyOf |
P68464
|
FINISHED |
| Object | Qing dynasty history |
—
|
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: Qing dynasty history | Statement: [Yongzheng, usedInChronologyOf, Qing dynasty history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInChronologyOf Context triple: [Yongzheng, usedInChronologyOf, Qing dynasty history]
-
A.
chronologyOf
chosen
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
B.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
C.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
D.
involvesChronology
Indicates that the relationship or action explicitly depends on, references, or organizes events according to their order or position in time.
-
E.
chronologicalSignificance
Indicates that one entity holds importance or relevance specifically due to its position, order, or timing within a chronological sequence relative to another.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcde51c408190afb34010b1707014 |
completed | April 2, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.