Triple
T4911782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiuchus |
E110248
|
entity |
| Predicate | visibleBetweenLatitudes |
P13005
|
FINISHED |
| Object | +80° and −80° |
—
|
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: +80° and −80° | Statement: [Ophiuchus, visibleBetweenLatitudes, +80° and −80°]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleBetweenLatitudes Context triple: [Ophiuchus, visibleBetweenLatitudes, +80° and −80°]
-
A.
visibleFromLatitudeNorth
Indicates that something can be seen or observed from locations at or north of a specified latitude.
-
B.
visibleFromLatitudeSouth
Indicates that something can be seen or observed from locations situated at or south of a specified latitude.
-
C.
isBestSeenFromLatitudes
Indicates that something is most optimally or clearly observable when viewed from specific geographic latitudes.
-
D.
liesWithinLatitudeBand
chosen
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
E.
regionLongitudeRange
Indicates the longitudinal span or interval that defines the east–west extent of a region.
- 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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e9c32148190a940a3733ecd1898 |
completed | March 20, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.