Triple
T4515614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dvapara Yuga |
E102145
|
entity |
| Predicate | hasConceptOfTime |
P57133
|
FINISHED |
| Object | cyclical time |
—
|
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: cyclical time | Statement: [Dvapara Yuga, hasConceptOfTime, cyclical time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConceptOfTime Context triple: [Dvapara Yuga, hasConceptOfTime, cyclical time]
-
A.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
B.
hasTemporalUse
Indicates that something is used, applicable, or valid only during a specific time or temporal interval.
-
C.
depictionOfTime
Indicates that one entity visually represents or symbolizes a specific moment, period, or progression of time associated with another entity.
-
D.
hasChronologicalPhase
Indicates that something is associated with, or occurs during, a specific chronological phase or time period in a sequence of development or events.
-
E.
chronologicalFunction
Indicates a temporal relationship where one event or state functions to order, structure, or position another within a sequence of time.
- F. None of above. chosen
Provenance (4 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5725745c81908bb462ba9537ae14 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.