Triple
T20561367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth-199999 |
E504849
|
entity |
| Predicate | hasCosmicEntity |
P90440
|
FINISHED |
| Object | Celestials |
—
|
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: Celestials | Statement: [Earth-199999, hasCosmicEntity, Celestials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCosmicEntity Context triple: [Earth-199999, hasCosmicEntity, Celestials]
-
A.
cosmicForce
Indicates a powerful, often supernatural or universal influence exerted on or between entities, typically affecting them beyond ordinary physical interactions.
-
B.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
-
C.
cosmicInteraction
Indicates an interaction or influence occurring between cosmic or astronomical entities or phenomena.
-
D.
hasInUniverseInhabitants
chosen
Indicates that a universe or fictional setting contains certain beings or populations as its inhabitants.
-
E.
cosmicDimension
Indicates a relationship where something exists, operates, or is characterized within a particular cosmic or universal scale, realm, or dimension.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a79ec10481909740eb6a08ae2658 |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.