Triple
T29611899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amon Göth |
E754747
|
entity |
| Predicate | operatedCamp |
P167720
|
FINISHED |
| Object | Płaszów 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: Płaszów concentration camp | Statement: [Amon Göth, operatedCamp, Płaszów concentration camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedCamp Context triple: [Amon Göth, operatedCamp, Płaszów concentration camp]
-
A.
operatesFieldCamp
Indicates that an entity manages and runs the activities of a field camp at a given location or for a specified purpose.
-
B.
campingManagedBy
Indicates that the organization or entity specified is responsible for managing, operating, or overseeing the camping activity, site, or facility.
-
C.
hasCampOperator
chosen
Indicates that a camp is operated or managed by a specific operator or organization.
-
D.
operatedAmong
Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
-
E.
administeredCamp
Indicates that an entity was responsible for managing, organizing, or overseeing the operation of a particular camp.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
Created at: April 28, 2026, 6:29 p.m.