Triple
T29768327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha Muscae |
E753976
|
entity |
| Predicate | isMostLuminousMemberOf |
P133141
|
FINISHED |
| Object | Musca |
—
|
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: Musca | Statement: [Alpha Muscae, isMostLuminousMemberOf, Musca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMostLuminousMemberOf Context triple: [Alpha Muscae, isMostLuminousMemberOf, Musca]
-
A.
isAmongBrightestMembersOf
Indicates that an entity is one of the most luminous or outstanding members within a specified group or set.
-
B.
isMostMassiveStarOf
Indicates that one star is the most massive member within a specified group, system, or context of stars.
-
C.
isAmongBrightestInConstellation
Indicates that an astronomical object ranks among the most luminous members within its specified constellation.
-
D.
isBrightestInAssociation
chosen
Indicates that an object is the most luminous member within a specified association or group.
-
E.
isForegroundStarOfCluster
Indicates that a star lies in the foreground along the line of sight to a star cluster, rather than being physically associated with the cluster itself.
- F. None of above.
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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745f8354819085a81de5c32dd49e |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 8:40 p.m.