Triple
T7140706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John T. Raulston |
E166431
|
entity |
| Predicate | trialTypePresidedOver |
P25382
|
FINISHED |
| Object | criminal 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: criminal trial | Statement: [John T. Raulston, trialTypePresidedOver, criminal trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialTypePresidedOver Context triple: [John T. Raulston, trialTypePresidedOver, criminal trial]
-
A.
trialHeldIn
Indicates that a legal trial took place or was conducted within a specified location or jurisdiction.
-
B.
trialName
Indicates the designated name or title assigned to a specific trial.
-
C.
typeOfProceedings
chosen
Indicates the specific category or kind of legal or formal process under which an action or case is being conducted.
-
D.
presidedAt
Indicates that one entity held a position of authority or leadership over the proceedings or activities that took place at a specific event or location.
-
E.
chamberPresidedOver
Indicates that one entity serves as the presiding authority or leader over the proceedings and activities of a specific chamber (such as a legislative or judicial body).
- 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_69c6888579d481909e05a8d6b81bf733 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7775e408190b880abde0a3f8d12 |
completed | March 27, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.