Triple
T3707905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khmer Rouge |
E80936
|
entity |
| Predicate | governedPeriodEnd |
P50928
|
FINISHED |
| Object | 1979-01-07 |
—
|
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: 1979-01-07 | Statement: [Khmer Rouge, governedPeriodEnd, 1979-01-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedPeriodEnd Context triple: [Khmer Rouge, governedPeriodEnd, 1979-01-07]
-
A.
associatedPeriodEnd
Indicates the ending point or final date of the time period with which something is associated.
-
B.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
-
C.
governedDuringPeriod
Indicates that a governing entity exercised authority or control over another entity throughout a specified time period.
-
D.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
timePeriodAsSeatOfGovernmentEnd
Indicates the point in time when a particular location ceases to serve as the seat of government for an entity.
- F. None of above. chosen
Provenance (4 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc580b08481908391283778d5ce14 |
completed | March 8, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:33 p.m.