Triple
T7860230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grini concentration camp |
E182476
|
entity |
| Predicate | hasWorkDetail |
P79422
|
FINISHED |
| Object | quarry 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: quarry labor | Statement: [Grini concentration camp, hasWorkDetail, quarry labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkDetail Context triple: [Grini concentration camp, hasWorkDetail, quarry labor]
-
A.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
B.
hasWorkOn
Indicates that one entity is associated with, contributes to, or performs work on another entity (such as a project, task, or artifact).
-
C.
hasWorkCount
Indicates the number of works (such as items, creations, or outputs) associated with a given entity.
-
D.
hasWorkProduct
Indicates that one entity produces, creates, or is responsible for a particular work product or output associated with it.
-
E.
hasWorkField
Indicates that an entity is associated with or operates within a particular field or area of work.
- F. None of above. chosen
Provenance (4 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_69ca82887fd48190975896bf38c4596b |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb36bb6ca4819098bc00739e07cfc8 |
completed | March 31, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69cae925ca388190ae4a01fa76e957e8 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf786ec748190b6347b0c94335550 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:53 p.m.