Triple
T467570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Central Standard Time |
E8481
|
entity |
| Predicate | hasHalfHourOffset |
P15081
|
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: [Australian Central Standard Time, hasHalfHourOffset, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHalfHourOffset Context triple: [Australian Central Standard Time, hasHalfHourOffset, true]
-
A.
isOneHourAheadOf
Indicates that one entity’s local time is exactly one hour later than the other entity’s local time.
-
B.
isTwoHoursBehind
Indicates that one entity’s time zone or clock is exactly two hours earlier than another entity’s time zone or clock.
-
C.
hasDaylightSavingVariant
Indicates that one time-related entity is the daylight saving time version or counterpart of another standard-time entity.
-
D.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
isThreeHoursBehind
Indicates that one entity’s time zone or local time is exactly three hours earlier than another entity’s.
- F. None of above. chosen
Provenance (4 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd9bea081909ee782840f3da12b |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edebb3988190907992a584b4e260 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef257a548190a96bfa0cf6183976 |
completed | Feb. 28, 2026, 1:35 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.