Triple
T4515615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dvapara Yuga |
E102145
|
entity |
| Predicate | belongsToConceptualSystem |
P531
|
FINISHED |
| Object | Hindu time cycles |
—
|
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: Hindu time cycles | Statement: [Dvapara Yuga, belongsToConceptualSystem, Hindu time cycles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToConceptualSystem Context triple: [Dvapara Yuga, belongsToConceptualSystem, Hindu time cycles]
-
A.
partOfConcept
Indicates that one concept is a constituent or component of a larger, more encompassing concept.
-
B.
hasConcept
chosen
Indicates that an entity includes, embodies, or is associated with a particular concept.
-
C.
hasSubConcept
Indicates that one concept is a more specific, subordinate, or narrower idea within the scope of another, more general concept.
-
D.
hasConceptualOrigin
Indicates that something conceptually originates from, is derived from, or is fundamentally based on another thing.
-
E.
hasConceptualBoundary
Indicates that one entity defines, marks, or establishes the abstract limit or scope of another entity’s meaning, applicability, or conceptual extent.
- 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_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. |
Created at: March 20, 2026, 1:02 p.m.