Triple
T30625103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakshusha Manu |
E779553
|
entity |
| Predicate | universePhase |
P49707
|
FINISHED |
| Object | current kalpa of Brahma |
—
|
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: current kalpa of Brahma | Statement: [Chakshusha Manu, universePhase, current kalpa of Brahma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: universePhase Context triple: [Chakshusha Manu, universePhase, current kalpa of Brahma]
-
A.
linkedToUniversePhase
chosen
Indicates that something is associated or connected to a particular phase or stage of the universe’s evolution or lifecycle.
-
B.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
-
C.
universeStatus
Indicates the current overall state or condition of a universe within a given system or context.
-
D.
universeNumber
Indicates that an entity is associated with a specific universe identified by a particular number or index.
-
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_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:27 p.m.