Triple
T23367313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diphda |
E593358
|
entity |
| Predicate | rankInNightSkyBrightness |
P67062
|
FINISHED |
| Object | among the brighter stars in the night sky |
—
|
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: among the brighter stars in the night sky | Statement: [Diphda, rankInNightSkyBrightness, among the brighter stars in the night sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInNightSkyBrightness Context triple: [Diphda, rankInNightSkyBrightness, among the brighter stars in the night sky]
-
A.
rankByBrightnessInNightSky
chosen
Indicates the relative ordering of celestial objects based on how bright they appear in the night sky.
-
B.
isProminentInNightSky
Indicates that an astronomical object is easily visible and stands out in the night sky due to its brightness, size, or position.
-
C.
meteorBrightness
Indicates the observed luminous intensity or apparent brightness of a meteor during its visible passage.
-
D.
apparentBrightness
Indicates how bright one object appears from the perspective or location of another, regardless of its actual intrinsic luminosity.
-
E.
visibleInEveningSky
Indicates that the entity can be seen in the sky during evening hours.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0ad621881908a909f236e6e9c90 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.