Triple
T22935058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austral Kingdom |
E569556
|
entity |
| Predicate | spansLatitudeRange |
P130596
|
FINISHED |
| Object | subtropical to subantarctic zones |
—
|
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: subtropical to subantarctic zones | Statement: [Austral Kingdom, spansLatitudeRange, subtropical to subantarctic zones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spansLatitudeRange Context triple: [Austral Kingdom, spansLatitudeRange, subtropical to subantarctic zones]
-
A.
regionLongitudeRange
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
B.
liesWithinLatitudeBand
Indicates that one geographic entity is located within a specified range of latitudes defined as a latitude band.
-
C.
visibleAtLatitudeBetween
Indicates that something can be seen or is observable only within a specified range of latitudes.
-
D.
latitudeRangeApproximate
Indicates that the latitude of an entity falls within an approximate or loosely bounded range, rather than an exact or strictly defined interval.
-
E.
extendsLatitude
chosen
Indicates that one entity’s spatial extent reaches across or beyond the latitude range associated with another entity.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181350c7881908a72dc7a30e1aaff |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.