Triple
T28248886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canicula |
E712261
|
entity |
| Predicate | isMostVisibleIn |
P150588
|
FINISHED |
| Object | winterSkyNorthernHemisphere |
—
|
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: winterSkyNorthernHemisphere | Statement: [Canicula, isMostVisibleIn, winterSkyNorthernHemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMostVisibleIn Context triple: [Canicula, isMostVisibleIn, winterSkyNorthernHemisphere]
-
A.
isViewableIn
Indicates that one entity can be visually accessed, observed, or displayed within the context, medium, or viewpoint defined by another entity.
-
B.
isVisibleBestIn
chosen
Indicates that an entity is considered the most visible or prominent within a specified context or set.
-
C.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
D.
isPartiallyVisibleFrom
Indicates that one entity can be seen only in part, rather than fully, from the viewpoint or location of another entity.
-
E.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11:03 p.m.