Triple
T3392144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. [Accused] |
E71443
|
entity |
| Predicate | accusedRole |
P46944
|
FINISHED |
| Object | criminal defendant |
—
|
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 defendant | Statement: [United States v. [Accused], accusedRole, criminal defendant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accusedRole Context triple: [United States v. [Accused], accusedRole, criminal defendant]
-
A.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
B.
accusedOf
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
C.
accusedCharacterPortrayedBy
Indicates that a particular actor or performer plays the role of the character who is accused within a given work.
-
D.
roleInCrime
chosen
Indicates the specific function, responsibility, or participation an entity has within the commission of a particular crime.
-
E.
accusedGroup
Indicates that one group is formally charged or blamed by another party for committing a wrongdoing or offense.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb850594c81909b6f8a384fc98cb2 |
completed | March 8, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.