Triple
T25475640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hinckley Jr. |
E638422
|
entity |
| Predicate | confinedUntil |
P36798
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [John Hinckley Jr., confinedUntil, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confinedUntil Context triple: [John Hinckley Jr., confinedUntil, 2016]
-
A.
detainedUntil
chosen
Indicates that an entity is held in custody or confinement up to a specified time or until a particular condition is met.
-
B.
confinedFrom
Indicates that one entity is restricted, imprisoned, or kept within a place or condition as a result of another entity’s action or authority.
-
C.
leaderImprisonedUntil
Indicates that a leader is held in imprisonment up to and including a specified point in time.
-
D.
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).
-
E.
detainedAfter
Indicates that one entity is held in custody or confinement following another specified event or action.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f754447c8190acc16c440f8bb03d |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 2:26 p.m.