Triple
T2184580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zulu time |
E49120
|
entity |
| Predicate | timeZoneDesignationType |
P4820
|
FINISHED |
| Object | military time zone |
—
|
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: military time zone | Statement: [Zulu time, timeZoneDesignationType, military time zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneDesignationType Context triple: [Zulu time, timeZoneDesignationType, military time zone]
-
A.
timeZoneDesignation
Indicates the specific time zone label or code assigned to an entity for representing its local time.
-
B.
timeZoneType
chosen
Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
-
C.
timeZoneRegionType
Indicates the classification of a time zone based on the type of geographic or administrative region it is associated with.
-
D.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
-
E.
DSTTimeZone
Indicates that a time-related entity operates under a daylight saving time rule or belongs to a time zone that observes daylight saving time adjustments.
- 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_69a88aa72d348190a9544bb5b8a4e71d |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.