Triple
T21884773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamma Leporis |
E540375
|
entity |
| Predicate | BayerDesignation |
P24821
|
FINISHED |
| Object | γ Leporis |
—
|
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: γ Leporis | Statement: [Gamma Leporis, BayerDesignation, γ Leporis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: γ Leporis Context triple: [Gamma Leporis, BayerDesignation, γ Leporis]
-
A.
Gamma Lupi
Gamma Lupi is a multiple star system in the southern constellation Lupus, visible to the naked eye and composed of hot, massive B-type stars.
-
B.
Beta Leporis
Beta Leporis, traditionally named Nihal, is a bright yellow giant star in the constellation Lepus located near Orion in the night sky.
-
C.
Gamma Leporis B
Gamma Leporis B is the fainter stellar companion in the Gamma Leporis binary system, located in the constellation Lepus.
-
D.
Gamma Leporis A
chosen
Gamma Leporis A is the primary star in the Gamma Leporis binary system, a nearby Sun-like main-sequence star located in the constellation Lepus.
-
E.
Alpha Lyncis
Alpha Lyncis is the brightest star in the constellation Lynx, visible as an orange giant in the northern 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118eabb008190ab6f1364ef4e6feb |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 16, 2026, 7:05 p.m.