Triple
T21188502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6664 |
E522148
|
entity |
| Predicate | hasGalacticObjectType |
P143216
|
FINISHED |
| Object | open cluster |
—
|
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: open cluster | Statement: [NGC 6664, hasGalacticObjectType, open cluster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGalacticObjectType Context triple: [NGC 6664, hasGalacticObjectType, open cluster]
-
A.
hasGalaxyType
Indicates that a galaxy is classified as belonging to a specific morphological or structural type.
-
B.
isInGalaxy
Indicates that one astronomical object is located within or belongs to a particular galaxy.
-
C.
containsGalaxy
Indicates that one entity spatially includes or encompasses a galaxy as part of its contents or structure.
-
D.
hasGalacticContext
Indicates that something is associated with, situated within, or characterized by a broader galactic-scale environment or framework.
-
E.
hasGalacticCoordinateSystem
Indicates that something is associated with or defined within a particular galactic coordinate system.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333403448190bcd9cc0805e414b5 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:07 p.m.