Triple
T20972887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sphere of the Sun |
E516547
|
entity |
| Predicate | positionInHeavens |
P49587
|
FINISHED |
| Object | fourth heaven |
—
|
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: fourth heaven | Statement: [Sphere of the Sun, positionInHeavens, fourth heaven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInHeavens Context triple: [Sphere of the Sun, positionInHeavens, fourth heaven]
-
A.
positionInCosmos
chosen
Indicates the spatial or hierarchical location of an entity within the broader structure of the cosmos or universe.
-
B.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
C.
positionInConstellation
Indicates the specific location or role an object occupies within the boundaries or structure of a given constellation.
-
D.
positionInCosmogony
Indicates the role or place an entity occupies within a culture’s creation or origin narrative of the universe.
-
E.
positionInAsterism
Indicates the specific location or role that an object occupies within a defined asterism pattern.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba161d88190b8905891f449004e |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:45 p.m.