Triple

T121243
Position Surface form Disambiguated ID Type / Status
Subject Alaska Time Zone E2447 entity
Predicate typicalBusinessHourEndLocalTime P2917 FINISHED
Object 17: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: 17:00 | Statement: [Alaska Time Zone, typicalBusinessHourEndLocalTime, 17:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalBusinessHourEndLocalTime
Context triple: [Alaska Time Zone, typicalBusinessHourEndLocalTime, 17:00]
  • A. officeEnded
    Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
  • B. hasTradingHours chosen
    Indicates that an entity operates or is available for trading during specified time periods.
  • C. DSTEndRule
    Indicates the rule or condition that specifies when daylight saving time ends in a given timekeeping system.
  • D. endDate
    Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
  • E. commercialPeak
    Indicates the time or period when something (such as a product, artist, or business) achieves its highest level of commercial success or popularity.
  • 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_69a2506c5428819085c28a8884790e29 completed Feb. 28, 2026, 2:18 a.m.
NER Named-entity recognition batch_69a258fd278481908ad4498e03f38e2f completed Feb. 28, 2026, 2:54 a.m.
PD Predicate disambiguation batch_69a25647fe6081908cb0405266d35ff5 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:24 a.m.