Triple
T127575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albert Kesselring |
E2582
|
entity |
| Predicate | convictedBy |
P6535
|
FINISHED |
| Object | British military court |
—
|
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: British military court | Statement: [Albert Kesselring, convictedBy, British military court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convictedBy Context triple: [Albert Kesselring, convictedBy, British military court]
-
A.
punishedBy
Indicates that an entity receives punishment administered by another entity.
-
B.
prosecuted
Indicates that legal authorities have formally brought criminal charges against an entity and pursued a case against them in a court of law.
-
C.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
-
D.
confessedTo
Indicates that one entity admitted guilt or revealed the truth about an action, wrongdoing, or secret to another entity.
-
E.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25761e9248190a7205bfc36cb5c45 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2575d8a648190ad8e10d4b04e5e07 |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.