Triple
T2812943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August Kranti Day |
E54214
|
entity |
| Predicate | relatedEventDate |
P830
|
FINISHED |
| Object | 9 August 1942 |
—
|
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: 9 August 1942 | Statement: [August Kranti Day, relatedEventDate, 9 August 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEventDate Context triple: [August Kranti Day, relatedEventDate, 9 August 1942]
-
A.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
B.
associatedEventType
Indicates that one entity is linked to another by the type or category of event with which it is associated.
-
C.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
D.
calendarLinkedTo
Indicates that one calendar is connected or synchronized with another calendar or calendaring system so that events or updates can be shared or reflected between them.
-
E.
timeOfEventCommemorated
Indicates the specific time or date at which the event being commemorated originally occurred.
- 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_69ab49de0af08190b3da69683be1e728 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde4a31d081909377044d5ff791b0 |
completed | March 7, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69abdd0740208190911dc9c9546a79ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.