Triple
T22929704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Time Clock |
E569401
|
entity |
| Predicate | numberOfTimeZonesDisplayed |
P137773
|
FINISHED |
| Object | 24 |
—
|
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 | Statement: [World Time Clock, numberOfTimeZonesDisplayed, 24]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfTimeZonesDisplayed Context triple: [World Time Clock, numberOfTimeZonesDisplayed, 24]
-
A.
hasNumberOfNationalTimeZones
Indicates the quantity of distinct official time zones that a nation or country uses within its territory.
-
B.
zoneCount
chosen
Indicates the number of distinct zones associated with or contained within a given entity or context.
-
C.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
D.
numberOfTimeZonesCrossed
Indicates the count of distinct time zones that an entity passes through or traverses during a specified journey or process.
-
E.
offsetRangeOfTimeZones
Indicates that one entity specifies the span or limits of time zone offsets (e.g., from minimum to maximum UTC offsets) applicable to another entity.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180dc33e8819099e5ad87207de57f |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:44 p.m.