Triple
T18476772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kali Yuga |
E451453
|
entity |
| Predicate | startMarkedBy |
P1408
|
FINISHED |
| Object | departure of Krishna from earth |
—
|
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: departure of Krishna from earth | Statement: [Kali Yuga, startMarkedBy, departure of Krishna from earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startMarkedBy Context triple: [Kali Yuga, startMarkedBy, departure of Krishna from earth]
-
A.
stallMarkedBy
Indicates that a stall or booth is identified or distinguished by a particular mark, label, or sign.
-
B.
entranceMarkedBy
Indicates that the entrance of one entity is distinguished or identified by the presence of another entity (such as a sign, marker, or feature).
-
C.
initiatedBy
chosen
Indicates that an action, event, or process was started or set in motion by a particular entity.
-
D.
constructionStartedBy
Indicates that the construction of something was initiated or begun by a particular agent or entity.
-
E.
initiatedIn
Indicates that an action, process, or event was started or first brought into effect within a specified context, such as a place, time, or situation.
- 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.