Triple
T19382281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLIMPSE survey |
E484840
|
entity |
| Predicate | hostGalaxyComponent |
P136229
|
FINISHED |
| Object | Galactic disk |
—
|
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: Galactic disk | Statement: [GLIMPSE survey, hostGalaxyComponent, Galactic disk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostGalaxyComponent Context triple: [GLIMPSE survey, hostGalaxyComponent, Galactic disk]
-
A.
hostGalaxy
Indicates the galaxy in which an astronomical object or system is located or with which it is physically associated.
-
B.
hostGalaxyGroup
Indicates that one entity serves as the galaxy group in which the other entity (typically a galaxy or astronomical object) is hosted or embedded.
-
C.
hostGalaxyConstellation
Indicates the constellation in which the host galaxy of an object is located.
-
D.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
-
E.
hostOrbit
Indicates that one celestial body orbits around another body that serves as its primary gravitational host.
- F. None of above. chosen
Provenance (4 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a614cf88190b561eafaa350ce19 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:35 p.m.