Triple
T24911735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lon Nol |
E623863
|
entity |
| Predicate | succeededByInPower |
P4400
|
FINISHED |
| Object | Khmer Rouge regime |
—
|
NE NERFINISHED |
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: Khmer Rouge regime | Statement: [Lon Nol, succeededByInPower, Khmer Rouge regime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByInPower Context triple: [Lon Nol, succeededByInPower, Khmer Rouge regime]
-
A.
successorPowers
Indicates that one entity has inherited authority, control, or responsibilities from another, functioning as its successor in power.
-
B.
successorPowerContext
Indicates that one entity holds or exercises power or authority as a successor within a particular contextual or situational framework.
-
C.
successorHasWiderPowers
Indicates that the successor entity holds broader or more extensive powers or authority than its predecessor.
-
D.
cameToPowerAfter
chosen
Indicates that one entity assumed authority or control following the rule or tenure of another entity.
-
E.
heldBySuccessorOf
Indicates that something is possessed, controlled, or occupied by an entity that is the successor of another specified 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 5:28 a.m.