Triple
T22999806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cr 189 |
E572603
|
entity |
| Predicate | isOneOfMostProminentOpenClusters |
P150589
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cr 189, isOneOfMostProminentOpenClusters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneOfMostProminentOpenClusters Context triple: [Cr 189, isOneOfMostProminentOpenClusters, true]
-
A.
isBrightestOpenClusterIn
Indicates that one open star cluster is the most luminous (brightest) among all open clusters within a specified region or context.
-
B.
cataloguedAsOpenCluster
Indicates that an astronomical object has been classified in a catalog as an open star cluster.
-
C.
isOneOfNearestOpenClustersToEarth
Indicates that the subject cluster is among the closest open star clusters to Earth in terms of spatial distance.
-
D.
isForegroundStarOfCluster
Indicates that a star lies in the foreground along the line of sight to a star cluster, rather than being physically associated with the cluster itself.
-
E.
isNearbyOpenCluster
Indicates that one entity is an open star cluster located at a relatively close spatial distance to the other 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f6484c8190bfe3f7ea894c43d8 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:50 p.m.