Triple
T17088354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkes Airport |
E414658
|
entity |
| Predicate | DST UTC offset |
P713
|
FINISHED |
| Object | +11 |
—
|
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: +11 | Statement: [Parkes Airport, DST UTC offset, +11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DST UTC offset Context triple: [Parkes Airport, DST UTC offset, +11]
-
A.
DSTIsAheadOfUTC
Indicates that the time in a region observing Daylight Saving Time is ahead of Coordinated Universal Time (UTC) by a specified offset.
-
B.
DSTOffsetType
Indicates the relationship between a time reference and the amount of time it is shifted from standard time due to daylight saving time adjustments.
-
C.
UTCOffsetDaylightSavingTime
chosen
Indicates the time difference from Coordinated Universal Time (UTC) that applies to an entity specifically during daylight saving time periods.
-
D.
offsetDSTApprox
Indicates an approximate time offset between entities that accounts for daylight saving time adjustments.
-
E.
DSTComparedToStandardTime
Indicates that a time value is expressed relative to standard time, specifying whether and how it is adjusted for Daylight Saving Time.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe92e488190b947287a968086d5 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.