Triple
T8594098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anhui clique |
E203499
|
entity |
| Predicate | afterDefeatOutcome |
P48782
|
FINISHED |
| Object | loss of control over Beijing government |
—
|
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: loss of control over Beijing government | Statement: [Anhui clique, afterDefeatOutcome, loss of control over Beijing government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterDefeatOutcome Context triple: [Anhui clique, afterDefeatOutcome, loss of control over Beijing government]
-
A.
significantDefeat
Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
-
B.
defeat
Indicates that one entity wins against and overcomes another in a contest, conflict, or competition.
-
C.
aftermathOf
chosen
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
D.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
E.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.