Triple
T25475642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hinckley Jr. |
E638422
|
entity |
| Predicate | unconditionalReleaseDate |
P158580
|
FINISHED |
| Object | 2022-06-15 |
—
|
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: 2022-06-15 | Statement: [John Hinckley Jr., unconditionalReleaseDate, 2022-06-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unconditionalReleaseDate Context triple: [John Hinckley Jr., unconditionalReleaseDate, 2022-06-15]
-
A.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
B.
releasedFor
Indicates that something has been made available or authorized for public use, distribution, or access.
-
C.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
D.
relievedOnDate
Indicates that an entity was formally released, discharged, or relieved from a role, duty, or obligation on a specific date.
-
E.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
- 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_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_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:26 p.m.