Triple
T3587628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPG/ESO 2.2 m Telescope |
E75948
|
entity |
| Predicate | hemisphereCoverage |
P40962
|
FINISHED |
| Object | southern 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: southern sky | Statement: [MPG/ESO 2.2 m Telescope, hemisphereCoverage, southern sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hemisphereCoverage Context triple: [MPG/ESO 2.2 m Telescope, hemisphereCoverage, southern sky]
-
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.
hasLandCoverage
Indicates that a specified area or region is covered or occupied by a particular type of land surface or land use.
-
D.
visibleInHemisphere
chosen
Indicates that an object or phenomenon can be seen or observed from a specified hemisphere of a celestial body.
-
E.
locatedInWesternHemisphere
Indicates that the subject is geographically situated within the Western Hemisphere of the Earth.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc13a11608190a23d76efc1b50e3c |
completed | March 8, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.