Triple

T38154435
Position Surface form Disambiguated ID Type / Status
Subject America/Moncton E952844 entity
Predicate historicalTimeChangesRecorded P12951 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/Moncton, historicalTimeChangesRecorded, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalTimeChangesRecorded
Context triple: [America/Moncton, historicalTimeChangesRecorded, true]
  • 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. historicalModification
    Indicates that one entity has altered, updated, or otherwise changed another entity at some point in the past, with the modification recorded as part of its history.
  • C. historicalRecord
    Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
  • D. historicallyRecordedSince
    Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
  • E. changesTimeline
    Indicates that one entity alters, restructures, or otherwise affects the sequence or scheduling of events associated with another entity.
  • 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_69f76f0a67f4819080c492f61d688fcc completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_6a0207a1272c81909dcdb6e3307702f5 completed May 11, 2026, 4:45 p.m.
PD Predicate disambiguation batch_6a0205fa1e608190829fd2baa0434fff completed May 11, 2026, 4:38 p.m.
Created at: May 3, 2026, 4:21 p.m.