Triple
T116222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Eastern Standard Time |
E2343
|
entity |
| Predicate | DSTObserved |
P384
|
FINISHED |
| Object | false in Queensland |
—
|
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: false in Queensland | Statement: [Australian Eastern Standard Time, DSTObserved, false in Queensland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DSTObserved Context triple: [Australian Eastern Standard Time, DSTObserved, false in Queensland]
-
A.
DSTStartRule
Indicates the rule or condition that determines when daylight saving time begins for a given time zone or region.
-
B.
DSTEndRule
Indicates the rule or condition that specifies when daylight saving time ends in a given timekeeping system.
-
C.
observesDaylightSavingTime
chosen
Indicates that an entity adjusts its standard time forward and backward according to a daylight saving time schedule.
-
D.
observesDaylightSavingWith
Indicates that one entity follows the same daylight saving time rules or schedule as another entity.
-
E.
DSTAbbreviation
Indicates that one entity is the standard abbreviated form used to represent another entity related to 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_69a2506c5428819085c28a8884790e29 |
completed | Feb. 28, 2026, 2:18 a.m. |
| NER | Named-entity recognition | batch_69a257845c548190bfb49409988d1c57 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a256456d908190b52c937fe6c4343f |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:24 a.m.