Triple
T10653387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Am Prepared to Die |
E251027
|
entity |
| Predicate | legalRoleOfSpeaker |
P16985
|
FINISHED |
| Object | accused |
—
|
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: accused | Statement: [I Am Prepared to Die, legalRoleOfSpeaker, accused]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalRoleOfSpeaker Context triple: [I Am Prepared to Die, legalRoleOfSpeaker, accused]
-
A.
legalSystemRole
Indicates the specific function, capacity, or position an entity holds within a legal or judicial system.
-
B.
legalCaseRole
chosen
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
-
C.
legalProfessionRole
Indicates that one entity holds or performs a specific professional role within the legal domain in relation to another entity or context.
-
D.
legalCitationRole
Indicates the specific role or function an entity has within a legal citation, such as being the cited authority, citing source, or related reference.
-
E.
roleAtCourt
Indicates the specific position, function, or status an entity holds within a court or courtly setting.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff85674819099bf40c9f4fede15 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.