Triple
T18771215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lupus |
E459019
|
entity |
| Predicate | bestSeenAtLatitudeRange |
P57018
|
FINISHED |
| Object | from +35° to −90° |
—
|
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: from +35° to −90° | Statement: [Lupus, bestSeenAtLatitudeRange, from +35° to −90°]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestSeenAtLatitudeRange Context triple: [Lupus, bestSeenAtLatitudeRange, from +35° to −90°]
-
A.
isBestSeenFromLatitudes
chosen
Indicates that something is most optimally or clearly observable when viewed from specific geographic latitudes.
-
B.
notVisibleFromLatitudesNorthOf
Indicates that the subject cannot be seen or observed from any location situated at latitudes north of the specified reference latitude.
-
C.
visibleFromLatitudeSouth
Indicates that something can be seen or observed from locations situated at or south of a specified latitude.
-
D.
visibleFromLatitudeNorth
Indicates that something can be seen or observed from locations at or north of a specified latitude.
-
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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e59335a01881908731371be1e27a6b |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.