Triple
T6124233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Calley |
E136555
|
entity |
| Predicate | timeInCustody |
P8398
|
FINISHED |
| Object | approximately 3.5 years |
—
|
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: approximately 3.5 years | Statement: [William Calley, timeInCustody, approximately 3.5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInCustody Context triple: [William Calley, timeInCustody, approximately 3.5 years]
-
A.
servedPrisonTime
Indicates that an entity has spent a period of time incarcerated in prison as a consequence of a legal sentence.
-
B.
durationOfImprisonment
chosen
Indicates the length of time that an entity is or was held in imprisonment.
-
C.
imprisonedFor
Indicates that one entity is held in detention or jail as a consequence of, or in connection with, a specific reason, action, or offense committed by another entity or itself.
-
D.
peakIncarcerationPeriod
Indicates the time period during which incarceration levels for the referenced entity were at their highest.
-
E.
detainedFor
Indicates that one entity is being held in custody or confinement because of, or as a consequence of, another entity (such as a reason, charge, or event).
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05c25976081909e0a40e07dff0b8a |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.