Triple
T942847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Large Magellanic Cloud |
E20343
|
entity |
| Predicate | regionOfSky |
P9997
|
FINISHED |
| Object | southern 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: southern celestial hemisphere | Statement: [Large Magellanic Cloud, regionOfSky, southern celestial hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfSky Context triple: [Large Magellanic Cloud, regionOfSky, southern celestial hemisphere]
-
A.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
B.
areaSquareDegrees
Indicates the extent of a region or object measured as an area on the sky in square degrees.
-
C.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
-
D.
celestialLocation
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
E.
rightAscension
Indicates the angular distance of an object measured eastward along the celestial equator from the vernal equinox, specifying its position in the sky.
- 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_69a4b3a1a4888190997adf56eb761431 |
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.