Triple
T2459030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M13 |
E54486
|
entity |
| Predicate | isNakedEyeObject |
P20410
|
FINISHED |
| Object | yes, under dark skies |
—
|
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: yes, under dark skies | Statement: [M13, isNakedEyeObject, yes, under dark skies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNakedEyeObject Context triple: [M13, isNakedEyeObject, yes, under dark skies]
-
A.
visibleToNakedEye
chosen
Indicates that something can be perceived directly without the aid of optical instruments such as telescopes, microscopes, or binoculars.
-
B.
visibleFromEarth
Indicates that the object can be observed from Earth, either with the naked eye or with appropriate instruments, under suitable viewing conditions.
-
C.
hasDeepSkyObject
Indicates that an entity is associated with or contains a specific deep-sky astronomical object (such as a galaxy, nebula, or star cluster).
-
D.
canBeSeenWith
Indicates that two entities are observable together in the same context, setting, or time.
-
E.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd49c5aa081909ab4f726a458b77f |
completed | March 7, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69abd0b199488190aa381b36593ae1ac |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:44 p.m.