Triple
T16608649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asha |
E403508
|
entity |
| Predicate | cosmicDimension |
P123519
|
FINISHED |
| Object | cosmic order |
—
|
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: cosmic order | Statement: [Asha, cosmicDimension, cosmic order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicDimension Context triple: [Asha, cosmicDimension, cosmic order]
-
A.
cosmologicalRealm
Indicates that one entity exists in, belongs to, or is associated with a particular cosmological realm or plane of existence relative to another.
-
B.
cosmicFunction
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
-
C.
cosmologicalScale
Indicates that the relationship or phenomenon is occurring, measured, or considered at the scale of the entire universe or its large-scale structure.
-
D.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
-
E.
cosmologicalFeature
Indicates a relationship where something is identified as a large-scale structure or characteristic of the universe, such as a cosmic object, pattern, or phenomenon in cosmology.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e36094920881908051eb0a52e08440 |
completed | April 18, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.