Triple
T28590494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby Line–Stanstead border crossing |
E723625
|
entity |
| Predicate | timezoneUS |
P38817
|
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: [Derby Line–Stanstead border crossing, timezoneUS, Eastern Time Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timezoneUS Context triple: [Derby Line–Stanstead border crossing, timezoneUS, Eastern Time Zone]
-
A.
timeZoneOnUSSide
chosen
Indicates that the referenced time zone is the one used on the United States side of a border, region, or cross-national context.
-
B.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
C.
timeZoneOfHomeCity
Indicates the time zone in which a person's home city is located.
-
D.
timezoneBasis
Indicates that one timezone is defined, measured, or interpreted in reference to another timezone as its underlying standard or point of comparison.
-
E.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:20 a.m.