Triple
T4463391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuremberg Milch Trial |
E98311
|
entity |
| Predicate | chargeDetail |
P55566
|
FINISHED |
| Object | use of forced 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: use of forced labor | Statement: [Nuremberg Milch Trial, chargeDetail, use of forced labor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeDetail Context triple: [Nuremberg Milch Trial, chargeDetail, use of forced labor]
-
A.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
B.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
C.
chargesBasedOn
Indicates that one party determines or applies a fee, price, or cost to another party or item according to a specified basis, criterion, or reference.
-
D.
chargeArrangement
Indicates an agreement or setup specifying how charges, fees, or payments are to be applied or managed between parties.
-
E.
billing
Indicates that one entity charges another entity for goods or services, typically by issuing an invoice or request for payment.
- 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_69b3454a7c608190944f5455c8031d73 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3567913788190ac4f28fbe63a4fa9 |
completed | March 13, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69b34f65f6448190abfadb2ae5658798 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff7018c81908ad8597e525c042b |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:34 p.m.