Triple

T33566985
Position Surface form Disambiguated ID Type / Status
Subject UTM E859785 entity
Predicate centralMeridianScaleFactor P60849 FINISHED
Object 0.9996 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: 0.9996 | Statement: [UTM, centralMeridianScaleFactor, 0.9996]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: centralMeridianScaleFactor
Context triple: [UTM, centralMeridianScaleFactor, 0.9996]
  • A. scaleFactorAtCentralMeridian chosen
    Indicates the ratio by which distances are scaled along the central meridian of a map projection relative to true ground distances.
  • B. centralMeridianSpacing
    Indicates the angular distance or spacing between central meridians used as reference longitudes in a coordinate or mapping system.
  • C. principalMeridianNumber
    Indicates the specific identifying number assigned to a principal meridian used as a reference line in a land or coordinate survey system.
  • D. referenceMeridian
    Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
  • E. principalMeridianState
    Indicates the association between a principal meridian and the state in which that meridian is officially used or defined.
  • 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_69fd44474ed48190ac372e4c88d762ed completed May 8, 2026, 2:02 a.m.
PD Predicate disambiguation batch_69fd41ef28a48190a66959be5c964461 completed May 8, 2026, 1:52 a.m.
Created at: May 1, 2026, 1:40 a.m.