Triple

T10559625
Position Surface form Disambiguated ID Type / Status
Subject Flagtown, New Jersey E249179 entity
Predicate UTC offset DST P713 FINISHED
Object −04:00 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: −04:00 | Statement: [Flagtown, New Jersey, UTC offset DST, −04:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UTC offset DST
Context triple: [Flagtown, New Jersey, UTC offset DST, −04:00]
  • A. UTCOffsetDaylightSavingTime chosen
    Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
  • B. DSTOffsetType
    Indicates the relationship between a time reference and the amount of time it is shifted from standard time due to daylight saving time adjustments.
  • C. UTCoffsetComparison
    Indicates a comparison between the time zone UTC offsets of two entities, specifying how their local times differ relative to Coordinated Universal Time.
  • D. timeZoneOriginDST
    Indicates that the relationship specifies the original time zone of an entity, including whether daylight saving time (DST) is in effect.
  • E. utcOffsetDescription
    Indicates the textual description of how far a time zone’s local time differs from Coordinated Universal Time (UTC), often including details like hours, minutes, and daylight saving adjustments.
  • 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_69d381c8bd708190acf3d275c908251e completed April 6, 2026, 9:50 a.m.
NER Named-entity recognition batch_69d5271e65688190bcf7931373d87f94 completed April 7, 2026, 3:47 p.m.
PD Predicate disambiguation batch_69d51901ff6c819095e7b528170a69dc completed April 7, 2026, 2:47 p.m.
Created at: April 6, 2026, 12:35 p.m.