Triple
T5609658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois–Indiana state line |
E147319
|
entity |
| Predicate | hasAdjacentTimeZone |
P721
|
FINISHED |
| Object | Central Time Zone (Illinois side) |
—
|
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: Central Time Zone (Illinois side) | Statement: [Illinois–Indiana state line, hasAdjacentTimeZone, Central Time Zone (Illinois side)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentTimeZone Context triple: [Illinois–Indiana state line, hasAdjacentTimeZone, Central Time Zone (Illinois side)]
-
A.
adjacentTimeZoneEast
chosen
Indicates that one time zone is directly to the east of another, sharing a common boundary without any intervening time zones.
-
B.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
C.
adjacentTimeZoneWest
Indicates that one time zone is directly to the west of another, sharing a common boundary without any other time zone in between.
-
D.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
E.
followedByTimeZone
Indicates that one time zone chronologically succeeds another in a defined ordering or sequence.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0211dfc88819097b6d4254a61f65a |
completed | March 22, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.