Triple
T18476773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kali Yuga |
E451453
|
entity |
| Predicate | startEraUsedIn |
P91459
|
FINISHED |
| Object | traditional Hindu chronology |
—
|
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: traditional Hindu chronology | Statement: [Kali Yuga, startEraUsedIn, traditional Hindu chronology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startEraUsedIn Context triple: [Kali Yuga, startEraUsedIn, traditional Hindu chronology]
-
A.
usedDuringEraOf
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
B.
usedEraName
chosen
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
C.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
D.
marksNewEraFor
Indicates that one event, development, or change signifies the beginning of a distinct new period or phase for another.
-
E.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53063c0108190be71247567b5241b |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.