Triple
T22849184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Ulaanbaatar |
E566310
|
entity |
| Predicate | timeZoneDatabaseZoneName |
P16765
|
FINISHED |
| Object | Asia/Ulaanbaatar |
—
|
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: Asia/Ulaanbaatar | Statement: [Asia/Ulaanbaatar, timeZoneDatabaseZoneName, Asia/Ulaanbaatar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneDatabaseZoneName Context triple: [Asia/Ulaanbaatar, timeZoneDatabaseZoneName, Asia/Ulaanbaatar]
-
A.
timeZoneDatabase
Indicates that there is an association between something (such as a system, service, or region) and a specific time zone database it uses or is defined by.
-
B.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
-
C.
timeZoneDatabaseFormat
chosen
Indicates that the relationship specifies the time zone using a standardized database format (such as the IANA/Olson time zone identifier).
-
D.
timeZoneArea
Indicates the geographic area or region for which a particular time zone is defined or applicable.
-
E.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e8aceb88190b137d17a7510fee4 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.