Triple
T32864540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadamar Euthanasia Centre |
E840611
|
entity |
| Predicate | subsequentTrials |
P45841
|
FINISHED |
| Object | German courts in Frankfurt |
—
|
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: German courts in Frankfurt | Statement: [Hadamar Euthanasia Centre, subsequentTrials, German courts in Frankfurt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentTrials Context triple: [Hadamar Euthanasia Centre, subsequentTrials, German courts in Frankfurt]
-
A.
trialAfter
chosen
Indicates that one trial or legal proceeding occurs subsequent to another in time or sequence.
-
B.
subsequentPractice
Indicates that one practice, activity, or exercise occurs after and in continuation of another in time.
-
C.
trialNumber
Indicates the ordinal position or sequence index of a specific trial within a series of trials.
-
D.
relatedTrial
Indicates that one trial is associated with another trial, typically through relevance, similarity, or shared context within a broader study or legal/experimental framework.
-
E.
subsequentCase
Indicates that one legal case follows another in time or procedural order, often relying on or referencing the earlier case.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:17 a.m.