Triple
T328229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse C |
E6566
|
entity |
| Predicate | hasDST |
P384
|
FINISHED |
| Object | observes daylight saving time |
—
|
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: observes daylight saving time | Statement: [Concourse C, hasDST, observes daylight saving time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDST Context triple: [Concourse C, hasDST, observes daylight saving time]
-
A.
DSTobserved
Indicates that daylight saving time is in effect or being observed for a given time, date, or location.
-
B.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
-
C.
DSTPolicy
Indicates a relationship where a timekeeping system follows a specific daylight saving time policy, defining how and when clocks are adjusted seasonally.
-
D.
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.
-
E.
observesDaylightSavingTime
chosen
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea98fa2c8190a5b44f4a26543a17 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94aab1c8190b8654708c87eeb91 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.