Triple
T22999814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melotte 88 |
E572604
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | M44 |
—
|
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: M44 | Statement: [Melotte 88, hasAlternativeName, M44]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M44 Context triple: [Melotte 88, hasAlternativeName, M44]
-
A.
M44
chosen
M44 is an open star cluster in the constellation Cancer, also known as the Beehive Cluster or Praesepe, and is one of the nearest and most prominent clusters visible to the naked eye.
-
B.
M44
M44 is a Hungarian expressway that serves as a major road connection in the country’s national highway network.
-
C.
M45
M45 is the Pleiades, a prominent open star cluster in the constellation Taurus visible to the naked eye and known since antiquity.
-
D.
M-44
M-44 is a state highway in western Michigan that serves as a key route connecting Grand Rapids with surrounding communities.
-
E.
M-4
M-4 is a major Russian federal highway that runs from Moscow to the Black Sea coast, serving as a key transport corridor in the country.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f6484c8190bfe3f7ea894c43d8 |
completed | April 29, 2026, 4:03 a.m. |
Created at: April 17, 2026, 3:50 p.m.