Triple
T18775632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bow of Sagittarius |
E459125
|
entity |
| Predicate | bestVisibleInMonthRange |
P36410
|
FINISHED |
| Object | June to September |
—
|
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: June to September | Statement: [Bow of Sagittarius, bestVisibleInMonthRange, June to September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestVisibleInMonthRange Context triple: [Bow of Sagittarius, bestVisibleInMonthRange, June to September]
-
A.
bestVisibleMonthNorthernHemisphere
chosen
Indicates the month in which something is most optimally visible from locations in the Northern Hemisphere.
-
B.
visibleBestInMonth
Indicates that something is the most prominent or highest-ranked among visible items within a given month.
-
C.
isViewableIn
Indicates that one entity can be visually accessed, observed, or displayed within the context, medium, or viewpoint defined by another entity.
-
D.
hasMonth
Indicates that something is associated with, occurs in, or is assigned to a specific month.
-
E.
proposedInMonth
Indicates that an entity (such as a proposal or plan) was formally proposed during a specific calendar month.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933ad4288190b17e5fad57d8417d |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.