Triple
T6026253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fedor Reingold |
E134188
|
entity |
| Predicate | judicialProcessType |
P25382
|
FINISHED |
| Object | political trial |
—
|
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: political trial | Statement: [Fedor Reingold, judicialProcessType, political trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: judicialProcessType Context triple: [Fedor Reingold, judicialProcessType, political trial]
-
A.
typeOfProceedings
chosen
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
-
B.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
C.
typeOfJusticeMechanism
Indicates the kind or category of justice mechanism that characterizes how justice is pursued or administered in a given context.
-
D.
hasTypeOfCourt
Indicates that an entity is associated with or classified by a specific type or category of court.
-
E.
courtStyle
Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
- 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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0560cdc308190b25ca8ecb42c4e4f |
completed | March 22, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.