Triple
T13346672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherman, Ohio |
E317968
|
entity |
| Predicate | observesStandardTimeAbbreviation |
P714
|
FINISHED |
| Object | EST |
—
|
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: EST | Statement: [Sherman, Ohio, observesStandardTimeAbbreviation, EST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observesStandardTimeAbbreviation Context triple: [Sherman, Ohio, observesStandardTimeAbbreviation, EST]
-
A.
DSTAbbreviation
Indicates that one entity is the standard abbreviated form used to represent another entity related to daylight saving time.
-
B.
observesCentralStandardTime
Indicates that an entity follows Central Standard Time as its primary time zone for timekeeping or scheduling.
-
C.
observedAsStandardTimeIn
Indicates that a particular time standard is used as the official or standard time within a specified place or region.
-
D.
abbreviationStandardTime
chosen
Indicates that one entity is the standard-time abbreviation (e.g., non-daylight-saving time short form) for the other entity.
-
E.
observesDaylightSavingTimeFor
Indicates that one entity follows or applies a specific daylight saving time scheme or rule for another entity (such as a place, time zone, or period).
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e89c65c819093f3bea11d6073c5 |
completed | April 11, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69d98f6e53d88190bd6aa42f69b10ffb |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:31 p.m.