Triple
T25475641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hinckley Jr. |
E638422
|
entity |
| Predicate | releasedUnderConditions |
P24521
|
FINISHED |
| Object | 2016-09 |
—
|
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-09 | Statement: [John Hinckley Jr., releasedUnderConditions, 2016-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedUnderConditions Context triple: [John Hinckley Jr., releasedUnderConditions, 2016-09]
-
A.
releaseCondition
chosen
Indicates the circumstances or requirements under which something is allowed to be released or made available.
-
B.
releasedUnder
Indicates that one entity is made available, distributed, or published according to the terms, conditions, or authority specified by another entity (such as a license, label, or governing framework).
-
C.
releasedInsteadOf
Indicates that one entity was released in place of, or as a substitute for, another entity that was not released.
-
D.
releasedUnderMoniker
Indicates that a work was released using a particular stage name, alias, or alternate moniker rather than the creator’s primary name.
-
E.
releasedOnDemandOf
Indicates that one entity is released or set free as a direct result of another entity’s request, order, or demand.
- 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_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 2:26 p.m.