Triple
T19291848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIP 17531 |
E482460
|
entity |
| Predicate | hasClusterDesignation |
P96993
|
FINISHED |
| Object | Pleiades member star |
—
|
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: Pleiades member star | Statement: [HIP 17531, hasClusterDesignation, Pleiades member star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClusterDesignation Context triple: [HIP 17531, hasClusterDesignation, Pleiades member star]
-
A.
hasCluster
chosen
Indicates that one entity possesses, contains, or is associated with a specific cluster or grouping of related elements.
-
B.
hasRegionDesignation
Indicates that an entity is assigned or associated with a specific regional classification or designation.
-
C.
hasCityDesignatedAs
Indicates that an entity has a specific city formally assigned or designated to it in a particular role or capacity.
-
D.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
E.
hasDesignationNearby
Indicates that one entity has a designation (such as a label, title, or marker) located in close physical or contextual proximity to another entity.
- 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_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. |
Created at: April 10, 2026, 1:31 p.m.