Triple
T24019159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attica Correctional Facility |
E594767
|
entity |
| Predicate | notableEventEndDate |
P80890
|
FINISHED |
| Object | September 13, 1971 |
—
|
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: September 13, 1971 | Statement: [Attica Correctional Facility, notableEventEndDate, September 13, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventEndDate Context triple: [Attica Correctional Facility, notableEventEndDate, September 13, 1971]
-
A.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
-
C.
chronologicalCoverageEnd
Indicates the point in time at which the temporal or chronological span of something (such as a resource, event, or record) comes to an end.
-
D.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
E.
tookPlaceUntil
chosen
Indicates that an event or situation occurred continuously or repeatedly up to a specified end time or date, after which it no longer took place.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a7b5848190849e7a0f035465b3 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:42 p.m.