Triple
T19766186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkansas–Texas border |
E474761
|
entity |
| Predicate | hasTimeZoneConsistency |
P3413
|
FINISHED |
| Object | Central Time Zone on both sides |
—
|
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 on both sides | Statement: [Arkansas–Texas border, hasTimeZoneConsistency, Central Time Zone on both sides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeZoneConsistency Context triple: [Arkansas–Texas border, hasTimeZoneConsistency, Central Time Zone on both sides]
-
A.
hasTimeZones
chosen
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
B.
hasTimeZoneNote
Indicates that there is an associated note or annotation providing additional information or clarification about a time zone.
-
C.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
D.
hasTimeOffset
Indicates that one temporal value is shifted or displaced from another by a specified amount of time.
-
E.
isOneOfLastTimeZonesToExperienceDay
Indicates that an entity is located in a time zone where a given calendar day ends among the latest in the world, experiencing that day after most other time zones have already moved to the next day.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653232e508190a7d484c0a1e2939a |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.