Triple
T34793804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transverse Mercator |
E1003014
|
entity |
| Predicate | typicalZoneWidth |
P19786
|
FINISHED |
| Object | 6 degrees of longitude in UTM |
—
|
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: 6 degrees of longitude in UTM | Statement: [Transverse Mercator, typicalZoneWidth, 6 degrees of longitude in UTM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalZoneWidth Context triple: [Transverse Mercator, typicalZoneWidth, 6 degrees of longitude in UTM]
-
A.
zoneWidth
Indicates the measurement of how wide a specified zone or area is.
-
B.
centralZoneDiameter
Indicates the diameter measurement of the central zone of an object or region, typically from one side of the central area directly across to the opposite side.
-
C.
typicalWidth
chosen
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
D.
typicalZones
Indicates that certain spatial or contextual areas are characteristic or commonly associated with a given entity or situation.
-
E.
zoneType
Indicates the classification or category of a zone that specifies its type or functional designation.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.