Triple
T19261222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uranometria |
E481653
|
entity |
| Predicate | coversHemisphere |
P70356
|
FINISHED |
| Object | northern celestial hemisphere |
—
|
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: northern celestial hemisphere | Statement: [Uranometria, coversHemisphere, northern celestial hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversHemisphere Context triple: [Uranometria, coversHemisphere, northern celestial hemisphere]
-
A.
hemispherePresence
Indicates the spatial relationship of whether and in which hemisphere(s) (e.g., northern, southern, eastern, western) an entity is present or occurs.
-
B.
hasPeakUsageInHemisphere
Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
-
C.
visibleInHemisphere
Indicates that an object or phenomenon can be seen or observed from a specified hemisphere of a celestial body.
-
D.
hemisphereName
chosen
Indicates the named hemisphere (e.g., northern, southern, eastern, or western) that a given location or entity belongs to.
-
E.
hasProgenyInHemisphere
Indicates that an entity has offspring or descendants located within a specified hemisphere.
- 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_69d8e8ce54cc8190998418ff1f66ef28 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb890e7c8190beba407f63459382 |
completed | April 20, 2026, 10:10 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.