Triple
T14715323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunter Commission report on the Jallianwala Bagh massacre |
E345661
|
entity |
| Predicate | documentedEventDate |
P830
|
FINISHED |
| Object | 13 April 1919 |
—
|
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: 13 April 1919 | Statement: [Hunter Commission report on the Jallianwala Bagh massacre, documentedEventDate, 13 April 1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentedEventDate Context triple: [Hunter Commission report on the Jallianwala Bagh massacre, documentedEventDate, 13 April 1919]
-
A.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
C.
issuedDocumentDate
Indicates the date on which a document was formally created, released, or made officially valid by the issuing party.
-
D.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
E.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
- 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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98513b081908b230f6ac79c72ad |
completed | April 14, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69de657e174481909da0437556334a04 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:29 a.m.