Triple
T8253001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudolph Schnaubelt |
E193000
|
entity |
| Predicate | legalStatusInHaymarketCase |
P2250
|
FINISHED |
| Object | suspect |
—
|
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: suspect | Statement: [Rudolph Schnaubelt, legalStatusInHaymarketCase, suspect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInHaymarketCase Context triple: [Rudolph Schnaubelt, legalStatusInHaymarketCase, suspect]
-
A.
legalStatusAtIssue
Indicates that the legal status of an entity is the central subject of dispute, consideration, or determination in a legal context.
-
B.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
C.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
D.
legalStatusAfter1801
Indicates the legal status or condition of an entity as it existed or was defined after the year 1801.
-
E.
hasJurisdictionStatus
Indicates that an authority or entity holds a particular legal or administrative jurisdictional status over a specified domain, area, or matter.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78cbc7cc81909931440e95d6e691 |
completed | March 31, 2026, 7:33 a.m. |
| PD | Predicate disambiguation | batch_69cb36b6d5548190b665a6cce14c69f7 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.