Triple
T17939519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandi Chhor Divas |
E448549
|
entity |
| Predicate | historicalEventYearApprox |
P46780
|
FINISHED |
| Object | early 17th century |
—
|
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: early 17th century | Statement: [Bandi Chhor Divas, historicalEventYearApprox, early 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEventYearApprox Context triple: [Bandi Chhor Divas, historicalEventYearApprox, early 17th century]
-
A.
hasHistoricEventYear
Indicates the specific year in which a referenced historic event took place.
-
B.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
C.
nearHistoricalEventDate
Indicates that something occurs on a date that is close in time to a specified historical event’s date.
-
D.
hasHistoricalOriginInYear
Indicates that something first originated, began, or came into existence in a specified calendar year.
-
E.
yearCirca
chosen
Indicates that the associated year is approximate or uncertain rather than exact.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4ad9533688190bff773c183ed8505 |
completed | April 19, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:21 a.m.