Triple
T20613161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canopus |
E506496
|
entity |
| Predicate | rankByApparentBrightness |
P67062
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Canopus, rankByApparentBrightness, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankByApparentBrightness Context triple: [Canopus, rankByApparentBrightness, 2]
-
A.
rankByBrightnessInNightSky
chosen
Indicates the relative ordering of celestial objects based on how bright they appear in the night sky.
-
B.
apparentBrightness
Indicates how bright one object appears from the perspective or location of another, regardless of its actual intrinsic luminosity.
-
C.
rankByBrightnessInOrion
Indicates the ordering of entities based on their relative brightness within the Orion region.
-
D.
rankByDistanceFromSun
Indicates an ordering of entities based on how close or far they are from the Sun, with position determined by distance.
-
E.
apparentMagnitude
Indicates the observed brightness of an astronomical object as seen from Earth, on a logarithmic scale where lower values correspond to brighter appearances.
- 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_69e0b4bb2b4081908fa4a72444120f35 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aad94dac8190921c7769a649c724 |
completed | April 20, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69e5a00c43308190b7ea58d559257e07 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:41 a.m.