Triple
T22110732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 2261 |
E546408
|
entity |
| Predicate | illuminatedBy |
P38235
|
FINISHED |
| Object | R Monocerotis |
—
|
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: R Monocerotis | Statement: [NGC 2261, illuminatedBy, R Monocerotis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: R Monocerotis Context triple: [NGC 2261, illuminatedBy, R Monocerotis]
-
A.
R Monocerotis
chosen
R Monocerotis is a young, variable T Tauri star in the constellation Monoceros that serves as the illuminating source of Hubble’s Variable Nebula.
-
B.
S Monocerotis
S Monocerotis is a variable star system located in the constellation Monoceros, known for its brightness changes over time.
-
C.
Gamma Monocerotis
Gamma Monocerotis is a relatively bright star in the constellation Monoceros, visible to the naked eye and used as a reference point within this faint region of the night sky.
-
D.
Alpha Monocerotis
Alpha Monocerotis is a relatively bright giant star located in the constellation Monoceros, visible to the naked eye under good conditions.
-
E.
Rho Ursae Minoris
Rho Ursae Minoris is a relatively faint star located in the northern circumpolar constellation of Ursa Minor.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12948c2ec819083340787b2062649 |
completed | April 28, 2026, 9:40 p.m. |
Created at: April 16, 2026, 8:30 p.m.