Triple
T34921167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Jefferson General Hospital |
E1007140
|
entity |
| Predicate | operatesInTimezone |
P109
|
FINISHED |
| Object | Central Time Zone |
—
|
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: Central Time Zone | Statement: [East Jefferson General Hospital, operatesInTimezone, Central Time Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInTimezone Context triple: [East Jefferson General Hospital, operatesInTimezone, Central Time Zone]
-
A.
locatedInTimeZone
chosen
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
B.
isLocatedInTimeZoneRegion
Indicates that one entity exists within or is associated with the temporal boundaries defined by a specific time zone region.
-
C.
timeZoneRequirement
Indicates that a specific time zone or set of time zones is required or must be satisfied for the associated entity or activity.
-
D.
timeZoneImplication
Indicates that one time zone condition or setting logically leads to, constrains, or determines another time zone condition or setting.
-
E.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0119132e848190820a688d139fbf75 |
completed | May 10, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_6a01188dfdec8190b7f675264a281733 |
completed | May 10, 2026, 11:45 p.m. |
Created at: May 3, 2026, 4 p.m.