Triple
T22480600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Monocerotis |
E555753
|
entity |
| Predicate | otherName |
P39
|
FINISHED |
| Object | β Mon |
—
|
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: β Mon | Statement: [Beta Monocerotis, otherName, β Mon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: β Mon Context triple: [Beta Monocerotis, otherName, β Mon]
-
A.
Beta Monocerotis
chosen
Beta Monocerotis is a bright multiple-star system in the constellation Monoceros, notable for its visually striking trio of closely spaced, luminous stars.
-
B.
Beta Geminorum
Beta Geminorum, also known as Pollux, is the brightest star in the constellation Gemini and an orange giant located relatively close to Earth.
-
C.
Beta Gruis
Beta Gruis is a bright red giant star in the southern constellation Grus, visible to the naked eye and notable as one of its most luminous members.
-
D.
Beta Scorpii
Beta Scorpii is a bright multiple-star system in the constellation Scorpius, prominent in the night sky near the heart of the Scorpion.
-
E.
Beta Leporis
Beta Leporis, traditionally named Nihal, is a bright yellow giant star in the constellation Lepus located near Orion in the night sky.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3836a08190b6f0d88b94cb80a3 |
completed | April 29, 2026, 1:17 a.m. |
Created at: April 16, 2026, 8:49 p.m.