Triple
T18443847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6520 |
E450602
|
entity |
| Predicate | skyPositionRelation |
P9990
|
FINISHED |
| Object | near the Milky Way central bulge in projection |
—
|
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: near the Milky Way central bulge in projection | Statement: [NGC 6520, skyPositionRelation, near the Milky Way central bulge in projection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skyPositionRelation Context triple: [NGC 6520, skyPositionRelation, near the Milky Way central bulge in projection]
-
A.
celestialLocation
chosen
Indicates the spatial or positional relationship of an entity relative to a celestial body or region in space.
-
B.
spacePosition
Indicates the spatial location or coordinates of an entity within a defined space or reference frame.
-
C.
starsPosition
Indicates that one entity specifies the spatial location or coordinates of a star or group of stars relative to a reference frame.
-
D.
positionInConstellation
Indicates the specific location or role an object occupies within the boundaries or structure of a given constellation.
-
E.
starPosition
Indicates the spatial location or coordinates of a star relative to a defined reference frame.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c142abc8190b4f6f938acdc413d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.