Triple
T30624615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sage Manu |
E779537
|
entity |
| Predicate | cosmicRoleType |
P137962
|
FINISHED |
| Object | Manu (title of progenitor in each 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: Manu (title of progenitor in each manvantara) | Statement: [Sage Manu, cosmicRoleType, Manu (title of progenitor in each manvantara)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicRoleType Context triple: [Sage Manu, cosmicRoleType, Manu (title of progenitor in each manvantara)]
-
A.
roleInCosmos
Indicates the function, position, or significance an entity holds within the larger structure or order of the cosmos.
-
B.
cosmicRoleInTexts
chosen
Indicates the role or function an entity is described as having within cosmic or mythological contexts in texts.
-
C.
cosmologicalRoleOf
Indicates the role or function an entity plays within a cosmological framework or system.
-
D.
roleInMacrocosmica
Indicates that an entity has a specific role or function within a larger, overarching system or macro-level structure.
-
E.
roleInGalaxy
Indicates the specific function, status, or influence an entity holds within the broader structure or dynamics of a galaxy.
- 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_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:27 p.m.