Triple
T19291745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HD 23338 |
E482458
|
entity |
| Predicate | clusterDesignation |
P135150
|
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: [HD 23338, clusterDesignation, Melotte 22 member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clusterDesignation Context triple: [HD 23338, clusterDesignation, Melotte 22 member]
-
A.
communityDesignation
Indicates that an entity is formally assigned or recognized with a specific community-related status, label, or role.
-
B.
mapDesignation
Indicates a formal label or identifier that is assigned to something specifically for use on a map.
-
C.
cityPlanningDesignation
Indicates how an area is officially classified or designated within urban or municipal planning (e.g., residential, commercial, industrial).
-
D.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
E.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another entity.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc819a7881909a7afbd06d9dd3f0 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:31 p.m.