Triple
T29406133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNOME Clocks |
E745780
|
entity |
| Predicate | supportsTimeZones |
P204302
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [GNOME Clocks, supportsTimeZones, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTimeZones Context triple: [GNOME Clocks, supportsTimeZones, yes]
-
A.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
B.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
C.
timeZoneRequirement
Indicates that a specific time zone or set of time zones is required or must be satisfied for the associated entity or activity.
-
D.
timeZoneImplication
Indicates that one time zone condition or setting logically leads to, constrains, or determines another time zone condition or setting.
-
E.
hasNumberOfNationalTimeZones
Indicates the quantity of distinct official time zones that a nation or country uses within its territory.
- F. None of above. chosen
Provenance (4 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0379a4086c8190a83df5570f737e15 |
completed | May 12, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a037049db848190a6268bf1a8a60223 |
completed | May 12, 2026, 6:24 p.m. |
| PDg | Predicate description generation | batch_6a0379a33dc48190a29f72268c8ca8a8 |
completed | May 12, 2026, 7:04 p.m. |
Created at: April 28, 2026, 2:54 p.m.