Triple
T419884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Coquimbo |
E8076
|
entity |
| Predicate | isInHemisphere |
P1889
|
FINISHED |
| Object | Southern Hemisphere |
—
|
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: Southern Hemisphere | Statement: [Port of Coquimbo, isInHemisphere, Southern Hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInHemisphere Context triple: [Port of Coquimbo, isInHemisphere, Southern Hemisphere]
-
A.
hemispherePresence
chosen
Indicates the spatial relationship of whether and in which hemisphere(s) (e.g., northern, southern, eastern, western) an entity is present or occurs.
-
B.
hasPeakUsageInHemisphere
Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
-
C.
hasTropicOfCancerCrossing
Indicates that the specified entity is geographically intersected or crossed by the Tropic of Cancer.
-
D.
liesWithinLatitudeBand
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
E.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd3b948819097d96c73d0a0f699 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.