Triple
T19349457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursa Major II Dwarf Galaxy |
E483973
|
entity |
| Predicate | MilkyWayHemisphere |
P132944
|
FINISHED |
| Object | northern 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: northern sky | Statement: [Ursa Major II Dwarf Galaxy, MilkyWayHemisphere, northern sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MilkyWayHemisphere Context triple: [Ursa Major II Dwarf Galaxy, MilkyWayHemisphere, northern sky]
-
A.
locatedInMilkyWayArm
Indicates that one entity is situated within a specific spiral arm of the Milky Way galaxy in which the other entity (the arm) is defined.
-
B.
visibleInHemisphere
Indicates that an object or phenomenon can be seen or observed from a specified hemisphere of a celestial body.
-
C.
skyHemisphere
chosen
Indicates the celestial hemisphere (e.g., northern or southern part of the sky) in which an astronomical object or event is located or observed.
-
D.
MilkyWaySubgroup
Indicates that one astronomical object is a member of the Milky Way subgroup within the Local Group of galaxies.
-
E.
galacticCenterConstellation
Indicates the constellation in which the center of a given galaxy is located.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185d54c0819081715ca13a5806b4 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.