Triple
T8084550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Rockford |
E188697
|
entity |
| Predicate | criminalRecord |
P80418
|
FINISHED |
| Object | wrongfulImprisonment |
—
|
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: wrongfulImprisonment | Statement: [Jim Rockford, criminalRecord, wrongfulImprisonment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criminalRecord Context triple: [Jim Rockford, criminalRecord, wrongfulImprisonment]
-
A.
criminalStatus
Indicates the legal condition of an entity with respect to criminal law, such as whether they are accused, convicted, or cleared of a crime.
-
B.
crimeCharged
Indicates that legal authorities have formally accused an entity of committing a specific crime.
-
C.
convictedOf
Indicates that a person or entity has been found guilty of committing a specified offense or crime through a formal legal process.
-
D.
convictedIndividual
Indicates that an individual has been found guilty of a crime or offense through a formal legal process and has received a conviction.
-
E.
committedCrime
Indicates that an entity has carried out or been responsible for a criminal act or offense.
- F. None of above. chosen
Provenance (4 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb415e61ac81909e924aea69a7ff77 |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:29 p.m.