Triple
T3186955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israel Standard Time |
E66720
|
entity |
| Predicate | timeFormatCommon |
P2162
|
FINISHED |
| Object | 24-hour clock |
—
|
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: 24-hour clock | Statement: [Israel Standard Time, timeFormatCommon, 24-hour clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeFormatCommon Context triple: [Israel Standard Time, timeFormatCommon, 24-hour clock]
-
A.
timeNotation
chosen
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
B.
typicalFormatDuration
Indicates the usual or standard length of time associated with a particular format or presentation of something.
-
C.
timeStructure
Indicates that one entity defines, constrains, or organizes the temporal framework or schedule within which another entity exists or operates.
-
D.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
E.
standardTimeName
Indicates the official name assigned to a particular standard time used in a region or context.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada6c32ce88190a231be18d38ec5ba |
completed | March 8, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69ad9e04290481909092ddfbe6fdaabc |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.