Triple
T607927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bergen-Belsen |
E12033
|
entity |
| Predicate | siteUseAfterWar |
P14233
|
FINISHED |
| Object | displaced persons 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: displaced persons camp | Statement: [Bergen-Belsen, siteUseAfterWar, displaced persons camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteUseAfterWar Context triple: [Bergen-Belsen, siteUseAfterWar, displaced persons camp]
-
A.
notablePostwarUser
chosen
Indicates that an entity is recognized for its significant or prominent use of another entity in the period following a major war.
-
B.
postwarOutcome
Indicates the result or consequences that follow for a party or situation after a war has ended.
-
C.
garrisonAfterWar
Indicates that a military force is stationed in or occupies a location following the end of a war or major conflict.
-
D.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
E.
postwarActivity
Indicates activities, roles, or developments associated with an entity specifically in the period following a war or major conflict.
- 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_69a493309df48190a327f748e88049a6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49df34abc8190a578c8c2ab3d28e4 |
completed | March 1, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69a49cf8fc1c81908a9c7df552aa1a59 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.