Triple
T372097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belzec |
E8288
|
entity |
| Predicate | coverUpActions |
P9769
|
FINISHED |
| Object | bodies exhumed and burned |
—
|
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: bodies exhumed and burned | Statement: [Belzec, coverUpActions, bodies exhumed and burned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverUpActions Context triple: [Belzec, coverUpActions, bodies exhumed and burned]
-
A.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
B.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
C.
actsOn
chosen
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
D.
coversAdministration
Indicates that one entity is responsible for managing, overseeing, or handling the administrative aspects of another entity or activity.
-
E.
overrides
Indicates that one entity replaces, supersedes, or takes precedence over another in determining the outcome or applicable behavior.
- 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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec00785481908551fc3571fcca47 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e960d880819084b3df4e5137a1e2 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.