Triple
T12808254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asia/Ust-Nera |
E306200
|
entity |
| Predicate | timeZoneDatabaseVersionIntroduced |
P12948
|
FINISHED |
| Object | tz database version 2013a |
—
|
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: tz database version 2013a | Statement: [Asia/Ust-Nera, timeZoneDatabaseVersionIntroduced, tz database version 2013a]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneDatabaseVersionIntroduced Context triple: [Asia/Ust-Nera, timeZoneDatabaseVersionIntroduced, tz database version 2013a]
-
A.
timeZoneDatabaseVersioning
Indicates how versions are assigned, tracked, or managed for entries in a time zone database.
-
B.
timeZoneDatabase
chosen
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.
-
C.
timeZoneDatabaseFormat
Indicates that the relationship specifies the time zone using a standardized database format (such as the IANA/Olson time zone identifier).
-
D.
zoneSystemIntroduced
Indicates that a particular zone-based system has been formally brought into use or implemented.
-
E.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.