Triple

T16095400
Position Surface form Disambiguated ID Type / Status
Subject America/Detroit E390468 entity
Predicate historicalOffsetsMayVary P121878 FINISHED
Object true 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: true | Statement: [America/Detroit, historicalOffsetsMayVary, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalOffsetsMayVary
Context triple: [America/Detroit, historicalOffsetsMayVary, true]
  • A. historicalOffsetChanges
    Indicates that the relationship captures past changes in an offset value between entities, including when and how that offset was modified over time.
  • B. hasHistoricalShiftFrom
    Indicates a relationship where one state, practice, or condition has been replaced or transformed over time from another earlier state, practice, or condition.
  • C. hasHistoricalShiftTo
    Indicates a change over time in which one state, condition, or configuration is replaced or transformed into another in a historically traceable way.
  • D. historicalVersion
    Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
  • E. estimatedHistory
    Indicates that there is an inferred or approximated record of past states, events, or values associated with an entity or relationship.
  • F. None of above. chosen

Provenance (4 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_69d87f198bc48190a8b7e53ca15b7ead completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e1ff63edb0819092cbb671967bbdcd completed April 17, 2026, 9:37 a.m.
PD Predicate disambiguation batch_69e182804208819087f35307cd6e4103 completed April 17, 2026, 12:44 a.m.
PDg Predicate description generation batch_69e1ff5cd7e481908a29214139a3de2e completed April 17, 2026, 9:37 a.m.
Created at: April 10, 2026, 4:59 a.m.