Triple

T548242
Position Surface form Disambiguated ID Type / Status
Subject Australia/Brisbane E12778 entity
Predicate historicalChanges P12951 FINISHED
Object has had historical offset or rule changes recorded in tz database 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: has had historical offset or rule changes recorded in tz database | Statement: [Australia/Brisbane, historicalChanges, has had historical offset or rule changes recorded in tz database]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalChanges
Context triple: [Australia/Brisbane, historicalChanges, has had historical offset or rule changes recorded in tz database]
  • A. historicalOffsetChanges chosen
    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. historicalState
    Indicates that an entity existed in a particular state or condition during a specified time in the past.
  • D. hasHistoricalEntity
    Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical context.
  • E. administrativeHistory
    Indicates the sequence of past administrative changes, statuses, or governing arrangements that have affected an entity over time.
  • 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_69a49334226c81908b0ea1689ef6aa3f completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49900895c819092a131c185a758bf completed March 1, 2026, 7:52 p.m.
PD Predicate disambiguation batch_69a494b957988190bc269e372df2f0b2 completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.