Triple
T21433387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August Bebel |
E528745
|
entity |
| Predicate | imprisoned for |
P3353
|
FINISHED |
| Object | high treason |
—
|
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: high treason | Statement: [August Bebel, imprisoned for, high treason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imprisoned for Context triple: [August Bebel, imprisoned for, high treason]
-
A.
imprisonedFor
chosen
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
-
B.
hasBeenImprisoned
Indicates that an entity has been confined or incarcerated in a prison or similar detention facility at some point in time.
-
C.
imprisonedWith
Indicates that two entities are confined or held in prison together at the same time and place.
-
D.
hasBeenImprisonedBy
Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
-
E.
usedForImprisoning
Indicates that something serves as a means, tool, or method for confining or detaining someone against their will.
- 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_69e0c4569fa081908101baa24f8745db |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813fe2108190a4193f69667fe79e |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:59 p.m.