Triple

T26883295
Position Surface form Disambiguated ID Type / Status
Subject Saint Petersburg time (historical) E676969 entity
Predicate timeZoneCenterLongitude P1282 FINISHED
Object Saint Petersburg NE NERFINISHED

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: Saint Petersburg | Statement: [Saint Petersburg time (historical), timeZoneCenterLongitude, Saint Petersburg]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: timeZoneCenterLongitude
Context triple: [Saint Petersburg time (historical), timeZoneCenterLongitude, Saint Petersburg]
  • A. hostCityLongitude
    Indicates the longitudinal coordinate of the city that serves as the host location for an event or entity.
  • B. coordinateLongitude chosen
    Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
  • C. intendedLongitude
    Indicates the longitude value that an entity is meant or planned to have or reach, rather than its actual current longitude.
  • D. colongitude
    Indicates the angular distance of a point (typically on a rotating body) measured westward from a defined prime meridian, often used to specify its position relative to the body’s rotation or illumination.
  • E. typicalCityLongitude
    Indicates the standard or representative longitude value associated with a given city.
  • 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_69eee9bc0c90819085608c8bdc513a57 completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61fd623bc819091df736cf3419b99 completed May 2, 2026, 4:01 p.m.
PD Predicate disambiguation batch_69f61b3d23f481908dfec27adace900a completed May 2, 2026, 3:41 p.m.
Created at: April 27, 2026, 5:40 a.m.