Triple
T29552995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floß subcamp |
E749826
|
entity |
| Predicate | isSubcampOf |
P44138
|
FINISHED |
| Object | Flossenbürg 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: Flossenbürg concentration camp | Statement: [Floß subcamp, isSubcampOf, Flossenbürg concentration camp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubcampOf Context triple: [Floß subcamp, isSubcampOf, Flossenbürg concentration camp]
-
A.
hasSubcamps
chosen
Indicates that an entity includes or is associated with one or more subordinate or subsidiary camps.
-
B.
numberOfSubcamps
Indicates the total count of subordinate or subsidiary camps associated with a main camp.
-
C.
hasSubCampus
Indicates that an institution or main campus includes or is associated with a smaller, subordinate campus as part of its organizational structure.
-
D.
hasSubCampusArea
Indicates that a campus includes or is associated with a specific subordinate or component area within its overall grounds.
-
E.
hasSubcommunityIn
Indicates that a larger community contains or encompasses a smaller, distinct subcommunity located within it.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 5:13 p.m.