Triple

T4236
Position Surface form Disambiguated ID Type / Status
Subject University City, Philadelphia E81 entity
Predicate UTCOffsetStandard P109 FINISHED
Object UTC−05: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: UTC−05:00 | Statement: [University City, Philadelphia, UTCOffsetStandard, UTC−05:00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: UTCOffsetStandard
Context triple: [University City, Philadelphia, UTCOffsetStandard, UTC−05:00]
  • A. locatedInTimeZone chosen
    Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
  • B. ISOCode
    Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
  • C. hasDemonym
    Indicates that one entity is the term (demonym) used to refer to the inhabitants or natives of another entity (typically a place).
  • D. officialLanguage
    Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
  • E. notableStandard
    Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
  • 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_69a238d6b47881909e68288aed2fd858 completed Feb. 28, 2026, 12:37 a.m.
NER Named-entity recognition batch_69a23c24b3d08190a714126292fd5479 completed Feb. 28, 2026, 12:51 a.m.
PD Predicate disambiguation batch_69a23998af288190855f0456740cbd51 completed Feb. 28, 2026, 12:40 a.m.
Created at: Feb. 28, 2026, 12:40 a.m.