Triple
T16061071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xinyou Coup |
E389611
|
entity |
| Predicate | chronologyWithinDynasty |
P68464
|
FINISHED |
| Object | occurred shortly after the Second Opium War |
—
|
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: occurred shortly after the Second Opium War | Statement: [Xinyou Coup, chronologyWithinDynasty, occurred shortly after the Second Opium War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologyWithinDynasty Context triple: [Xinyou Coup, chronologyWithinDynasty, occurred shortly after the Second Opium War]
-
A.
chronologyWithinReignOf
Indicates that one event or time period occurs entirely within the span of a specified ruler’s reign.
-
B.
dynastyServed
Indicates that a person or group rendered service or allegiance to a particular ruling dynasty.
-
C.
chronologyOf
chosen
Indicates that one entity represents the temporal ordering, sequence, or historical timeline of events or states associated with another entity.
-
D.
dynastyConfirmed
Indicates that a particular ruling dynasty has been officially verified or recognized as legitimate in a given context.
-
E.
currentDynastyFoundedYear
Indicates the year in which the currently ruling dynasty was established or came into power.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.