Triple
T4619795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympian gods |
E100948
|
entity |
| Predicate | cosmicDomain |
P41871
|
FINISHED |
| Object | sky |
—
|
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: sky | Statement: [Olympian gods, cosmicDomain, sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmicDomain Context triple: [Olympian gods, cosmicDomain, sky]
-
A.
cosmologicalRealm
chosen
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.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
-
D.
cosmicAssociation
Indicates a relationship in which entities are linked, connected, or correlated through cosmic or celestial factors, influences, or contexts.
-
E.
cosmicInteraction
Indicates an interaction or influence occurring between cosmic or astronomical entities or phenomena.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e3e6948190925e2cfad20dcc8c |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.