Triple
T16531919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTM coordinate system |
E401586
|
entity |
| Predicate | zoneIdentification |
P2160
|
FINISHED |
| Object | zone number plus latitude band letter |
—
|
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: zone number plus latitude band letter | Statement: [UTM coordinate system, zoneIdentification, zone number plus latitude band letter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneIdentification Context triple: [UTM coordinate system, zoneIdentification, zone number plus latitude band letter]
-
A.
zone
chosen
Indicates that an entity is located within, associated with, or assigned to a particular geographic or conceptual area or zone.
-
B.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
-
C.
zoneConcept
Indicates that one entity is associated with, defined by, or operates within a particular zone or conceptual area specified by another entity.
-
D.
regionID
Indicates that an entity is associated with, located in, or belongs to a specific geographic or administrative region identified by this ID.
-
E.
timeZoneArea
Indicates the geographic area or region for which a particular time zone is defined or applicable.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32ed8075c81908ff47396879abd0c |
completed | April 18, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e2969fab208190ad64164d24748c45 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:15 a.m.