Triple
T6062331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judenrat |
E135062
|
entity |
| Predicate | sometimesAttempted |
P58482
|
FINISHED |
| Object | mitigation of German demands |
—
|
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: mitigation of German demands | Statement: [Judenrat, sometimesAttempted, mitigation of German demands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesAttempted Context triple: [Judenrat, sometimesAttempted, mitigation of German demands]
-
A.
wasTriedAt
Indicates that a legal case or judicial proceeding involving an entity took place at a specific court or location.
-
B.
triedAt
Indicates that an attempt to perform an action or achieve an outcome occurred at a specific time or place.
-
C.
triedBy
Indicates that an entity has made an attempt to perform an action on, or in relation to, another entity.
-
D.
attemptedAction
chosen
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
E.
wasTriedBy
Indicates that a legal case or charge involving an entity was examined and judged in a trial conducted by another entity (such as a court or judge).
- 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_69c00878d06881909ee78e88913bf890 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0572100e8819084c3174921a2d527 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049f031408190b08b2766237c5dd0 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.