Triple
T22057791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAO 112740 |
E545067
|
entity |
| Predicate | hasRankByBrightnessInOrion |
P66094
|
FINISHED |
| Object | third brightest star in Orion |
—
|
LITERAL 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: third brightest star in Orion | Statement: [SAO 112740, hasRankByBrightnessInOrion, third brightest star in Orion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankByBrightnessInOrion Context triple: [SAO 112740, hasRankByBrightnessInOrion, third brightest star in Orion]
-
A.
rankByBrightnessInOrion
Indicates the ordering of entities based on their relative brightness within the Orion region.
-
B.
brightnessRankInOrion
chosen
Indicates the relative ordering of a celestial object's brightness specifically among objects located in the Orion constellation.
-
C.
isAmongBrightestInConstellation
Indicates that an astronomical object ranks among the most luminous members within its specified constellation.
-
D.
rankByBrightnessInNightSky
Indicates the relative ordering of celestial objects based on how bright they appear in the night sky.
-
E.
isBrightestRankInCrux
Indicates that an entity holds the highest brightness rank among the members of the Crux constellation.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285959f48190b89527b3f9e7ab11 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.