Triple
T11788412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holocaust shootings in the Soviet Union |
E280328
|
entity |
| Predicate | executionSiteType |
P52430
|
FINISHED |
| Object | ravines |
—
|
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: ravines | Statement: [Holocaust shootings in the Soviet Union, executionSiteType, ravines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionSiteType Context triple: [Holocaust shootings in the Soviet Union, executionSiteType, ravines]
-
A.
keyExecutionSite
Indicates the location or context in which a key (e.g., cryptographic or access key) is actually used or executed.
-
B.
executionSide
Indicates which party or side in a transaction, contract, or interaction is responsible for performing or carrying out the specified action.
-
C.
operatesOnSiteType
chosen
Indicates that an entity conducts its operations or activities at, or in association with, a specified type of site or location.
-
D.
executionCoreType
Indicates the specific type or category of execution core (e.g., processing unit or engine) responsible for carrying out a given operation or task.
-
E.
executionDomain
Indicates the context, environment, or scope within which an action, process, or operation is carried out or valid.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.