Triple
T15780690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berga an der Elster |
E382605
|
entity |
| Predicate | hasWorldWarIIHistory |
P19660
|
FINISHED |
| Object | site of Nazi forced labor camp |
—
|
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: site of Nazi forced labor camp | Statement: [Berga an der Elster, hasWorldWarIIHistory, site of Nazi forced labor camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldWarIIHistory Context triple: [Berga an der Elster, hasWorldWarIIHistory, site of Nazi forced labor camp]
-
A.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
B.
statusDuringWorldWarII
chosen
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
C.
worldWar
Indicates a large-scale armed conflict involving multiple nations across different regions of the world, typically encompassing numerous battles, alliances, and theaters of war.
-
D.
worldWarIService
Indicates that an entity served or participated in military service during World War I.
-
E.
duringWorldWar
Indicates that one entity’s action, state, or relationship occurred within the temporal span of World War II.
- 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e053fea90081908e3fe4f91475bead |
completed | April 16, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.