Triple
T19688272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | April 12 Purge |
E472768
|
entity |
| Predicate | factionSupportedBy |
P18809
|
FINISHED |
| Object | right-wing Kuomintang faction |
—
|
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: right-wing Kuomintang faction | Statement: [April 12 Purge, factionSupportedBy, right-wing Kuomintang faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionSupportedBy Context triple: [April 12 Purge, factionSupportedBy, right-wing Kuomintang faction]
-
A.
coalitionSupportedBy
Indicates that a coalition receives backing, endorsement, or assistance from a specified supporting entity.
-
B.
factionStatus
Indicates the current state or condition of a faction in relation to a particular context, system, or other entities.
-
C.
supportedCouncil
Indicates that an entity provided backing, endorsement, or assistance to a council.
-
D.
allianceSupport
Indicates a cooperative relationship where one party provides assistance, resources, or backing to an ally within the context of an alliance.
-
E.
supporterOf
chosen
Indicates that one entity backs, advocates for, or provides assistance to another entity, cause, or organization.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420d39688190ad3a84dbffce4ffe |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.