Triple
T3468559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACDT |
E73196
|
entity |
| Predicate | standardTimeCounterpartFullName |
P9440
|
FINISHED |
| Object | Australian Central Standard Time |
—
|
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: Australian Central Standard Time | Statement: [ACDT, standardTimeCounterpartFullName, Australian Central Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTimeCounterpartFullName Context triple: [ACDT, standardTimeCounterpartFullName, Australian Central Standard Time]
-
A.
standardTimeCounterpart
chosen
Indicates that one time representation is the corresponding value expressed in a standard or canonical time format for the other.
-
B.
standardTimeName
Indicates the official name assigned to a particular standard time used in a region or context.
-
C.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
D.
daylightSavingTimeName
Indicates the specific name or label used for the time zone during daylight saving time.
-
E.
relatedTimeStandard
Indicates that one time-related entity is defined, interpreted, or aligned according to a particular time standard or reference timescale.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb376d288190abac85f2ffa853dc |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.