Triple
T21369546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wirt County, West Virginia |
E527015
|
entity |
| Predicate | hasTimezoneAbbreviationDST |
P2161
|
FINISHED |
| Object | EDT |
—
|
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: EDT | Statement: [Wirt County, West Virginia, hasTimezoneAbbreviationDST, EDT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimezoneAbbreviationDST Context triple: [Wirt County, West Virginia, hasTimezoneAbbreviationDST, EDT]
-
A.
DSTAbbreviation
chosen
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
-
B.
hasDst
Indicates that one entity serves as the destination or target location of another entity.
-
C.
hasDSTComponent
Indicates that something includes or is associated with a component related to Daylight Saving Time (DST) behavior or configuration.
-
D.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
-
E.
includesTimeZoneAbbreviation
Indicates that something explicitly contains or specifies a time zone abbreviation as part of its representation or data.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0ad04e081908ff02b2ee2bc7485 |
completed | April 22, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:09 p.m.