Triple
T20584178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 6231 |
E505739
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Cr 315 |
—
|
NE NERFINISHED |
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: Cr 315 | Statement: [NGC 6231, hasAlternativeName, Cr 315]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cr 315 Context triple: [NGC 6231, hasAlternativeName, Cr 315]
-
A.
Cr 315
chosen
Cr 315 is an open star cluster designation in the Collinder catalog corresponding to the bright young cluster NGC 6231 in the constellation Scorpius.
-
B.
Cr 362
Cr 362 is an open star cluster in the constellation Sagittarius, better known as Messier 21.
-
C.
Cr 228
Cr 228 is an open star cluster in the Carina constellation, associated with the Carina Nebula region.
-
D.
Cr 189
Cr 189 is an open star cluster in the constellation Cancer, better known as the Beehive Cluster or Praesepe, one of the nearest and most prominent clusters visible to the naked eye.
-
E.
Cr 232
Cr 232 is an open star cluster in the constellation Carina, listed in the Collinder catalogue of star clusters.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b9669c8190b8e81fc72817d42c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a975f098819083700593a9fa6cd0 |
completed | April 20, 2026, 10:32 p.m. |
Created at: April 16, 2026, 11:40 a.m.