Triple
T18603639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Temperate Zone |
E454682
|
entity |
| Predicate | latitudeRangeApproximate |
P132754
|
FINISHED |
| Object | 23.5°S to 66.5°S |
—
|
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: 23.5°S to 66.5°S | Statement: [South Temperate Zone, latitudeRangeApproximate, 23.5°S to 66.5°S]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latitudeRangeApproximate Context triple: [South Temperate Zone, latitudeRangeApproximate, 23.5°S to 66.5°S]
-
A.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
B.
altitudeRange_m
Indicates the range of altitudes, measured in meters, over which the relationship or condition holds.
-
C.
regionLongitudeRange
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
D.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
-
E.
rangeCityApprox
Indicates that an entity is located within an approximate geographic range of a specified city, rather than at an exact or strictly defined boundary.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54752abec8190a5f4aa84abe8b240 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:45 a.m.