Triple
T24761594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monroe, Ohio |
E619457
|
entity |
| Predicate | hasTimeConventionDST |
P42564
|
FINISHED |
| Object | UTC−04:00 |
—
|
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: UTC−04:00 | Statement: [Monroe, Ohio, hasTimeConventionDST, UTC−04:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeConventionDST Context triple: [Monroe, Ohio, hasTimeConventionDST, UTC−04:00]
-
A.
hasDst
Indicates that one entity serves as the destination or target location of another entity.
-
B.
hasDSTComponent
chosen
Indicates that something includes or is associated with a component related to Daylight Saving Time (DST) behavior or configuration.
-
C.
usesDSTNotationChange
Indicates that a system or context applies a change in notation or representation when switching between standard time and daylight saving time.
-
D.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
-
E.
hasStandardTimeUTCOffset
Indicates the fixed difference in hours and minutes between an entity’s standard (non-daylight-saving) local time and Coordinated Universal Time (UTC).
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:27 a.m.