Triple
T30624885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaivasvata Manu |
E779544
|
entity |
| Predicate | cosmicTimePeriod |
P87196
|
FINISHED |
| Object | Vaivasvata Manvantara |
—
|
NE NERFINISHED |
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: Vaivasvata Manvantara | Statement: [Vaivasvata Manu, cosmicTimePeriod, Vaivasvata Manvantara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicTimePeriod Context triple: [Vaivasvata Manu, cosmicTimePeriod, Vaivasvata Manvantara]
-
A.
cosmologicalPeriod
chosen
Indicates a temporal relationship where something occurs, exists, or is defined within a specific cosmological era or phase of the universe.
-
B.
cosmicDurationType
Indicates the type or category of a time duration in a cosmic or astronomical context (e.g., epochs, eras, or other large-scale time spans).
-
C.
galacticEra
Indicates the specific galactic time period or epoch in which an event, state, or relationship occurs.
-
D.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
E.
cosmologicalRealm
Indicates that one entity exists in, belongs to, or is associated with a particular cosmological realm or plane of existence relative to another.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a18eee08190b6d3d752e1685177 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:27 p.m.