Triple
T7646271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil administratif de Versoix |
E173129
|
entity |
| Predicate | zoneHoraire |
P12624
|
FINISHED |
| Object | heure d’Europe centrale |
—
|
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: heure d’Europe centrale | Statement: [Conseil administratif de Versoix, zoneHoraire, heure d’Europe centrale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneHoraire Context triple: [Conseil administratif de Versoix, zoneHoraire, heure d’Europe centrale]
-
A.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
-
B.
capitalTimeZoneOf
Indicates that a specified time zone is the primary or official time zone in which a given capital city is located or operates.
-
C.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
-
D.
timeZoneDesignation
chosen
Indicates the specific time zone label or code assigned to an entity for representing its local time.
-
E.
timeZoneEndpoint
Indicates a connection or boundary point where a specific time zone applies or is defined.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faf3bd388190a8cb0f13322a7c00 |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e9ef1c81909c8bff716541ac1f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:58 p.m.