Triple
T23533082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Standard Time |
E576620
|
entity |
| Predicate | usedInAviationTimezoneDesignation |
P72793
|
FINISHED |
| Object | UTC+8 |
—
|
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: UTC+8 | Statement: [Singapore Standard Time, usedInAviationTimezoneDesignation, UTC+8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAviationTimezoneDesignation Context triple: [Singapore Standard Time, usedInAviationTimezoneDesignation, UTC+8]
-
A.
timeZoneDesignation
Indicates the specific time zone label or code assigned to an entity for representing its local time.
-
B.
airportTimeZone
Indicates the time zone in which an airport is located or operates.
-
C.
usedInAviationCharts
Indicates that something is employed or referenced within aviation charts for navigation, planning, or informational purposes.
-
D.
ICAOTypeDesignator
Indicates the standardized aircraft type code assigned by ICAO that specifies the model or family of an aircraft used in aviation operations and documentation.
-
E.
usedInAviationCodeContext
chosen
Indicates that something is employed or referenced within the context of aviation-related codes or coding systems.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac79800081908907bce55b9c68cf |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:10 p.m.