Triple
T30578262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pen Sovan |
E778308
|
entity |
| Predicate | wasInstalledAfter |
P103640
|
FINISHED |
| Object | Vietnamese-backed overthrow of the Khmer Rouge regime |
—
|
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: Vietnamese-backed overthrow of the Khmer Rouge regime | Statement: [Pen Sovan, wasInstalledAfter, Vietnamese-backed overthrow of the Khmer Rouge regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInstalledAfter Context triple: [Pen Sovan, wasInstalledAfter, Vietnamese-backed overthrow of the Khmer Rouge regime]
-
A.
installedAfter
chosen
Indicates that one installation event occurred later in time than another installation event.
-
B.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
C.
installedFor
Indicates that something has been set up or put in place to be used by or on behalf of a particular entity.
-
D.
installedBy
Indicates that one entity was set up, put in place, or made operational through the actions or intervention of another entity.
-
E.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:23 p.m.