Triple
T12760994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WVHA Trial at Nuremberg |
E304993
|
entity |
| Predicate | tribunalNumber |
P106760
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [WVHA Trial at Nuremberg, tribunalNumber, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribunalNumber Context triple: [WVHA Trial at Nuremberg, tribunalNumber, 4]
-
A.
courtNumber
Indicates the specific numbered court (e.g., field, room, or venue) assigned or associated with an event, case, or match.
-
B.
judicialCircuitNumber
Indicates the specific numbered judicial circuit with which an entity (such as a court or case) is associated.
-
C.
hasTribunal
Indicates that an entity is associated with or subject to a specific tribunal, such as a court or adjudicative body, that has authority over its cases or matters.
-
D.
caseNumber
Indicates the unique identifying number assigned to a particular legal or administrative case.
-
E.
tribunalConstitutedBy
Indicates that a tribunal is formed, established, or composed by a specified authority, body, or set of members.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8e44188190840cd23d380bf23d |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96409739881909174ba005a986cb5 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:28 p.m.