Triple
T12808293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Ust-Nera |
E306200
|
entity |
| Predicate | olsonFormatName |
P12953
|
FINISHED |
| Object | Asia/Ust-Nera |
E306200
|
NE 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/Ust-Nera | Statement: [Asia/Ust-Nera, olsonFormatName, Asia/Ust-Nera]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asia/Ust-Nera Context triple: [Asia/Ust-Nera, olsonFormatName, Asia/Ust-Nera]
-
A.
Asia/Ust-Nera
chosen
Asia/Ust-Nera is an IANA time zone identifier used for the Ust-Nera region in Russia’s Sakha Republic.
-
B.
Asia/Chita
Asia/Chita is an IANA time zone identifier representing the local time observed in the Chita region of eastern Russia.
-
C.
Asia/Yakutsk
Asia/Yakutsk is the IANA time zone identifier representing Yakutsk Time, used in the Yakutsk region of Russia.
-
D.
Asia/Novokuznetsk
Asia/Novokuznetsk is an IANA time zone covering the Novokuznetsk region of Russia, aligned with Krasnoyarsk Time (UTC+7).
-
E.
Asia/Barnaul
Asia/Barnaul is an IANA time zone identifier used for the Barnaul region of Russia, corresponding to Krasnoyarsk Time (UTC+7).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68ec6556081909375fada79ddcb8c |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 9, 2026, 5:31 p.m.