Triple
T27134795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Buses |
E681652
|
entity |
| Predicate | operatedInCamp |
P77263
|
FINISHED |
| Object | Neuengamme concentration camp |
—
|
NE NERFINISHED |
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: Neuengamme concentration camp | Statement: [White Buses, operatedInCamp, Neuengamme concentration camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedInCamp Context triple: [White Buses, operatedInCamp, Neuengamme concentration camp]
-
A.
operatedConcentrationCamp
Indicates that an entity was responsible for running, managing, or administering the operations of a concentration camp.
-
B.
operatedInColony
Indicates that an entity conducted operations or activities within a specific colony.
-
C.
operatedHidingPlaceAt
Indicates that an entity managed or ran a particular hiding place at a specified time or during a certain period.
-
D.
isOperatedIn
chosen
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
-
E.
isPrisonCamp
Indicates that a location or facility functions as a prison camp, where people are confined and typically subjected to restrictive or punitive conditions.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 27, 2026, 9:06 a.m.