Triple
T31953036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston–Los Angeles |
E815831
|
entity |
| Predicate | originTimeZone |
P203199
|
FINISHED |
| Object | Eastern Time Zone |
—
|
NE NERFINISHED |
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: Eastern Time Zone | Statement: [Boston–Los Angeles, originTimeZone, Eastern Time Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originTimeZone Context triple: [Boston–Los Angeles, originTimeZone, Eastern Time Zone]
-
A.
timeZoneOriginDST
Indicates that the relationship specifies the original time zone of an entity, including whether daylight saving time (DST) is in effect.
-
B.
timeZoneOffsetOrigin
Indicates the time difference between an entity’s local time and a defined origin or reference time zone.
-
C.
timeZoneDestination
Indicates the time zone associated with the destination location in a given context or event.
-
D.
relatedTimeZone
Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
-
E.
timezoneBasis
Indicates that one timezone is defined, measured, or interpreted in reference to another timezone as its underlying standard or point of comparison.
- F. None of above. chosen
Provenance (4 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a013a251b4081908b43d85dd95586c5 |
completed | May 11, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_6a0137e4ea988190812173a5ff044098 |
completed | May 11, 2026, 1:59 a.m. |
| PDg | Predicate description generation | batch_6a013a24495c8190b1035e40c51559d1 |
completed | May 11, 2026, 2:08 a.m. |
Created at: May 1, 2026, 12:08 a.m.