Triple
T21410209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 17954 |
E528146
|
entity |
| Predicate | hasPleiadesClusterDesignation |
P33200
|
FINISHED |
| Object | Melotte 22 member |
—
|
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: Melotte 22 member | Statement: [HIP 17954, hasPleiadesClusterDesignation, Melotte 22 member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPleiadesClusterDesignation Context triple: [HIP 17954, hasPleiadesClusterDesignation, Melotte 22 member]
-
A.
hasGlieseDesignation
Indicates that an astronomical object is identified by a specific Gliese catalog designation.
-
B.
associatedStarCluster
Indicates that one entity is related to or grouped with a particular star cluster, such as being part of, located in, or otherwise linked to that cluster.
-
C.
belongsToStarCluster
chosen
Indicates that an astronomical object is a member of, or gravitationally bound to, a specific star cluster.
-
D.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
E.
hasEmbeddedStarCluster
Indicates that one astronomical object contains or includes a star cluster within its structure or boundaries.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b1b4d4608190a86a6cd279709b21 |
completed | April 22, 2026, 11:32 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:42 p.m.