Triple
T12852769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Mitchel |
E307364
|
entity |
| Predicate | causeOfConviction |
P42056
|
FINISHED |
| Object | seditious writings against British rule |
—
|
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: seditious writings against British rule | Statement: [John Mitchel, causeOfConviction, seditious writings against British rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfConviction Context triple: [John Mitchel, causeOfConviction, seditious writings against British rule]
-
A.
reasonForConviction
chosen
Indicates the specific offense or legal basis for which an individual was found guilty or convicted.
-
B.
convictedOf
Indicates that a person or entity has been found guilty of committing a specified offense or crime through a formal legal process.
-
C.
placeOfConviction
Indicates the location where a person was formally convicted of a crime or offense.
-
D.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
E.
dateOfConviction
Indicates the specific calendar date on which a person or entity was formally found guilty of an offense.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.