Triple
T30061259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neustadt an der Waldnaab subcamp |
E763890
|
entity |
| Predicate | typeOfLabor |
P1366
|
FINISHED |
| Object | industrial labor |
—
|
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: industrial labor | Statement: [Neustadt an der Waldnaab subcamp, typeOfLabor, industrial labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLabor Context triple: [Neustadt an der Waldnaab subcamp, typeOfLabor, industrial labor]
-
A.
laborActionType
Indicates the specific kind of labor-related action or event (such as a strike, lockout, or protest) that characterizes the relationship or situation.
-
B.
typeOfWork
chosen
Indicates the kind or category of work associated with or performed by an entity.
-
C.
labourOf
Indicates that one entity is the work, effort, or labor performed or contributed by another entity.
-
D.
laborProvision
Indicates the provision or supply of labor or workforce from one party to another for work or services.
-
E.
laborSystem
Indicates the type or structure of work organization, employment arrangements, and labor relations that govern how work is performed and managed.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: April 29, 2026, 6:57 p.m.