Triple
T32152304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Cronic |
E821190
|
entity |
| Predicate | defendantName |
P2238
|
FINISHED |
| Object | Harrison P. Cronic |
—
|
NE NERFINISHED |
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: Harrison P. Cronic | Statement: [United States v. Cronic, defendantName, Harrison P. Cronic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendantName Context triple: [United States v. Cronic, defendantName, Harrison P. Cronic]
-
A.
defendant
chosen
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.
hasDefendantAlternativeName
Indicates that an entity serving as a defendant is known or recorded under an alternative or additional name.
-
D.
defendantAbbreviation
Indicates that one entity is an abbreviated or shortened form of the name or designation of a defendant in a legal context.
-
E.
defendantLocation
Indicates the place or jurisdiction where the defendant is located or resides in relation to a legal matter.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 12:31 a.m.