Triple
T31744779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dover–Calais |
E810238
|
entity |
| Predicate | timeZoneAtDover |
P52359
|
FINISHED |
| Object | GMT/BST |
—
|
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: GMT/BST | Statement: [Dover–Calais, timeZoneAtDover, GMT/BST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneAtDover Context triple: [Dover–Calais, timeZoneAtDover, GMT/BST]
-
A.
timeZoneDestination
chosen
Indicates the time zone associated with the destination location in a given context or event.
-
B.
DSTTimeZone
Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes daylight saving time adjustments.
-
C.
ChathamStandardTimeOffsetDifference
Indicates the time difference between Chatham Standard Time and another time standard or zone.
-
D.
timeZoneOnUSSide
Indicates that the referenced time zone is the one used on the United States side of a border, region, or cross-national context.
-
E.
isThreeQuartersOfAnHourAheadOf
Indicates that one entity’s time occurs exactly 45 minutes later than the other entity’s time.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab4d00c88190ab770c94b20f1eb0 |
completed | May 3, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:26 p.m.