Triple
T34025377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Australia–New South Wales–Queensland tripoint |
E872493
|
entity |
| Predicate | hasTimeZoneBoundary |
P53378
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [South Australia–New South Wales–Queensland tripoint, hasTimeZoneBoundary, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeZoneBoundary Context triple: [South Australia–New South Wales–Queensland tripoint, hasTimeZoneBoundary, true]
-
A.
timeZoneBoundaryFor
chosen
Indicates that a given boundary or geographic region serves as the delimiting line for a specific time zone.
-
B.
hasTimeZoneDifferenceAlongBorder
Indicates that two adjacent regions share a border across which their official time zones differ.
-
C.
hasTimeZoneNote
Indicates that there is an associated note or annotation providing additional information or clarification about a time zone.
-
D.
hasTimezoneOnBothSides
Indicates that the relationship or connection spans or involves regions located in two different time zones.
-
E.
isInTimeZoneOffset
Indicates that one temporal entity occurs within, or is associated with, a specific time zone offset relative to a reference time standard (such as 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 1, 2026, 1:51 a.m.