Triple
T2233515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capricornus |
E49224
|
entity |
| Predicate | visibleFromLatitudeNorth |
P36413
|
FINISHED |
| Object | up to about +60° |
—
|
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: up to about +60° | Statement: [Capricornus, visibleFromLatitudeNorth, up to about +60°]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleFromLatitudeNorth Context triple: [Capricornus, visibleFromLatitudeNorth, up to about +60°]
-
A.
locatedInNorthernHemisphere
Indicates that the subject is geographically situated in the Northern Hemisphere of the Earth.
-
B.
isSouthernmostLatitudeWhereSunCanBeOverhead
Indicates the southernmost latitude on Earth at which the Sun can appear directly overhead (at the zenith) at some time during the year.
-
C.
locatedInTheNorthernHemisphere
Indicates that the subject entity is situated geographically within the northern half of the Earth, above the equator.
-
D.
distanceFromNorthPole
Indicates the measured spatial distance between a given entity’s location and the geographic North Pole.
-
E.
locatedNorthOf
Indicates that one entity is positioned geographically to the north of another entity.
- F. None of above. chosen
Provenance (4 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0913f1c8190ac9cfeb0f1c84a76 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.