Triple
T33567001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTM |
E859785
|
entity |
| Predicate | zoneExtentLatitude |
P132754
|
FINISHED |
| Object | between 80°S and 84°N approximately |
—
|
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: between 80°S and 84°N approximately | Statement: [UTM, zoneExtentLatitude, between 80°S and 84°N approximately]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneExtentLatitude Context triple: [UTM, zoneExtentLatitude, between 80°S and 84°N approximately]
-
A.
regionLongitudeRange
Indicates the longitudinal span or interval that defines the east–west extent of a region.
-
B.
extendsLatitude
Indicates that one entity’s spatial extent reaches across or beyond the latitude range associated with another entity.
-
C.
zoneWidth
Indicates the measurement of how wide a specified zone or area is.
-
D.
latitudeRangeApproximate
chosen
Indicates that the latitude of an entity falls within an approximate or loosely bounded range, rather than an exact or strictly defined interval.
-
E.
demandsBoundaryAtLatitude
Indicates that an entity asserts or requires that a boundary be established along a specific line of latitude.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f740ee548190a73daee3321d8264 |
completed | May 3, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.