Triple
T10594482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choeung Ek Genocide Center |
E250073
|
entity |
| Predicate | timeOfUseAsExecutionSite |
P43883
|
FINISHED |
| Object | late 1970s |
—
|
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: late 1970s | Statement: [Choeung Ek Genocide Center, timeOfUseAsExecutionSite, late 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfUseAsExecutionSite Context triple: [Choeung Ek Genocide Center, timeOfUseAsExecutionSite, late 1970s]
-
A.
keyExecutionSite
Indicates the location or context in which a key (e.g., cryptographic or access key) is actually used or executed.
-
B.
timeOfEvaluation
Indicates the specific time or moment at which an assessment, measurement, or judgment is made about an entity or situation.
-
C.
executedDuring
chosen
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
D.
usesTimingRules
Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
-
E.
executedIn
Indicates that an action or process is carried out or takes place within a specified location, context, or environment.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278bacd88190a50dedfa59b622fc |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.