Triple
T24120292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neuengamme concentration camp |
E597633
|
entity |
| Predicate | mainLaborSector |
P20603
|
FINISHED |
| Object | brickworks |
—
|
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: brickworks | Statement: [Neuengamme concentration camp, mainLaborSector, brickworks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainLaborSector Context triple: [Neuengamme concentration camp, mainLaborSector, brickworks]
-
A.
economicSectors
Indicates a relationship that associates entities with the economic sectors or industries in which they operate or to which they belong.
-
B.
hasIndustrialSector
chosen
Indicates that an entity is associated with, operates in, or belongs to a particular industrial sector or branch of economic activity.
-
C.
labour
Indicates that an entity performs work or exerts effort, typically in a productive, economic, or physical context, often for another entity or purpose.
-
D.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
E.
mainLaborLaw
Indicates that the referenced law is the primary or governing labor/employment law applicable to the situation or entities involved.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee2defc81909df55900769fef5b |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.