Triple
T458655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newfoundland Time Zone |
E7286
|
entity |
| Predicate | isOffsetFromNeighboringZone |
P4824
|
FINISHED |
| Object | 30 minutes |
—
|
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: 30 minutes | Statement: [Newfoundland Time Zone, isOffsetFromNeighboringZone, 30 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOffsetFromNeighboringZone Context triple: [Newfoundland Time Zone, isOffsetFromNeighboringZone, 30 minutes]
-
A.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
B.
isAdjacentTo
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
C.
usesOffsetFrom
chosen
Indicates that one entity determines or expresses its position, value, or behavior relative to another by applying a specified offset from that reference.
-
D.
adjacentTimeZoneEast
Indicates that one time zone is directly to the east of another, sharing a common boundary without any intervening time zones.
-
E.
isCanonicalZone
Indicates that a given zone is the primary, standard, or officially recognized version among possible alternatives.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efa4a6208190a8243a0e14f84f52 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede75b6c81908350103d21f22a03 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.