Triple
T2699525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eugene V. Debs |
E59195
|
entity |
| Predicate | reasonForConviction |
P42056
|
FINISHED |
| Object | opposition to U.S. involvement in World War I |
—
|
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: opposition to U.S. involvement in World War I | Statement: [Eugene V. Debs, reasonForConviction, opposition to U.S. involvement in World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForConviction Context triple: [Eugene V. Debs, reasonForConviction, opposition to U.S. involvement in World War I]
-
A.
convictedBy
Indicates that an authority, typically a court or judge, has formally found an entity guilty of a crime or offense.
-
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.
reasonForMurder
Indicates the motive or underlying cause that led someone to commit a murder.
-
E.
guiltyOf
Indicates that an entity has been judged or determined to have committed a particular offense, crime, or wrongful act.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda34ba508190be8e2c9e4052adfc |
completed | March 7, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd9ceec708190aa162399023b2273 |
completed | March 7, 2026, 7:54 a.m. |
Created at: March 6, 2026, 9:55 p.m.