Triple
T4939976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robertson Islands |
E110902
|
entity |
| Predicate | locatedInLatitudeBand |
P13005
|
FINISHED |
| Object | sub-Antarctic to Antarctic latitudes |
—
|
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: sub-Antarctic to Antarctic latitudes | Statement: [Robertson Islands, locatedInLatitudeBand, sub-Antarctic to Antarctic latitudes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLatitudeBand Context triple: [Robertson Islands, locatedInLatitudeBand, sub-Antarctic to Antarctic latitudes]
-
A.
liesWithinLatitudeBand
chosen
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
B.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
C.
locatedInNorthernHemisphere
Indicates that the subject is geographically situated in the Northern Hemisphere of the Earth.
-
D.
hasTropicOfCancerCrossing
Indicates that the specified entity is geographically intersected or crossed by the Tropic of Cancer.
-
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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd708a3dcc81908b6628864fe0db0a |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.