Triple
T25068404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Suns |
E627843
|
entity |
| Predicate | cosmicAxis |
P157602
|
FINISHED |
| Object | axis mundi |
—
|
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: axis mundi | Statement: [Five Suns, cosmicAxis, axis mundi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicAxis Context triple: [Five Suns, cosmicAxis, axis mundi]
-
A.
cosmicCenter
chosen
Indicates that one entity serves as the central or focal point around which other cosmic entities or structures are organized or defined.
-
B.
cosmicDimension
Indicates a relationship where something exists, operates, or is characterized within a particular cosmic or universal scale, realm, or dimension.
-
C.
cosmicOpposite
Indicates that one entity is the conceptual or metaphysical opposite of another within a cosmic or universal framework.
-
D.
cosmicAssociation
Indicates a relationship in which entities are linked, connected, or correlated through cosmic or celestial factors, influences, or contexts.
-
E.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599f6f50819097b8b4fc59ec9a81 |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:10 a.m.