Triple
T8717143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musca |
E206923
|
entity |
| Predicate | containsStar |
P1393
|
FINISHED |
| Object | Alpha Muscae |
E753976
|
NE FINISHED |
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: Alpha Muscae | Statement: [Musca, containsStar, Alpha Muscae]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alpha Muscae Context triple: [Musca, containsStar, Alpha Muscae]
-
A.
Alpha Muscae
chosen
Alpha Muscae is a hot, blue-white B-type giant star in the southern constellation Musca, notable as its most luminous member.
-
B.
Alpha Ophiuchi
Alpha Ophiuchi, traditionally known as Rasalhague, is the brightest star in the constellation Ophiuchus and a rapidly rotating A-type subgiant located relatively close to Earth.
-
C.
Eta Serpentis
Eta Serpentis is a bright K-type giant star located in the tail region of the constellation Serpens.
-
D.
Mu Serpentis
Mu Serpentis is a relatively bright A-type main-sequence star located in the tail region of the constellation Serpens.
-
E.
Kappa Tucanae
Kappa Tucanae is a star system located in the southern constellation Tucana.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd9c2a08190a65ab0ce573153d2 |
completed | March 31, 2026, 11:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf42998df88190a6eba28c2efb2030 |
completed | April 3, 2026, 4:31 a.m. |
Created at: March 30, 2026, 6:36 p.m.