Triple
T7255243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homma trial |
E157701
|
entity |
| Predicate | foundDefendant |
P39428
|
FINISHED |
| Object | guilty |
—
|
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: guilty | Statement: [Homma trial, foundDefendant, guilty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundDefendant Context triple: [Homma trial, foundDefendant, guilty]
-
A.
defendant
Indicates that an entity is the party accused or sued in a legal action or proceeding.
-
B.
coDefendant
Indicates that two or more parties are jointly named and involved as defendants in the same legal case or proceeding.
-
C.
defendantLocation
Indicates the place or jurisdiction where the defendant is located or resides in relation to a legal matter.
-
D.
hasDefendants
Indicates that one or more entities serve as defendants in relation to a particular legal case or proceeding.
-
E.
defendantStatus
chosen
Indicates the legal condition or standing of a defendant within a judicial or law-enforcement process.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6eaa0c76c81909fe43ed6938a13ea |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.