Triple
T943195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tartarus |
E20351
|
entity |
| Predicate | cosmologicalPosition |
P20412
|
FINISHED |
| Object | beneath Hades |
—
|
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: beneath Hades | Statement: [Tartarus, cosmologicalPosition, beneath Hades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmologicalPosition Context triple: [Tartarus, cosmologicalPosition, beneath Hades]
-
A.
positionInCosmogony
chosen
Indicates the role or place an entity occupies within a culture’s creation or origin narrative of the universe.
-
B.
cosmicFunction
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
-
C.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
D.
universe
Indicates that something pertains to, exists within, or is associated with the entirety of space, time, matter, and phenomena collectively referred to as the universe.
-
E.
hasCosmologicalConstantSign
Indicates whether the sign (positive, negative, or zero) of the cosmological constant is specified for a given cosmological model or scenario.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a2b1ec8190a2753ad3b3e8cc7a |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29dc8dc8190b9d33f70f8563d61 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.