Triple
T33772264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurovision Song Contest 1992 |
E865409
|
entity |
| Predicate | hostCountryTimeZone |
P30887
|
FINISHED |
| Object | Central European Summer Time |
—
|
NE NERFINISHED |
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: Central European Summer Time | Statement: [Eurovision Song Contest 1992, hostCountryTimeZone, Central European Summer Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCountryTimeZone Context triple: [Eurovision Song Contest 1992, hostCountryTimeZone, Central European Summer Time]
-
A.
timeZoneOfHomeCity
Indicates the time zone in which a person's home city is located.
-
B.
timeZoneOfHostCity
chosen
Indicates the time zone in which the host city of an event or entity is located.
-
C.
timeZoneRegionOf
Indicates that a time zone is the official or primary time zone used within a specified geographic region.
-
D.
timeZoneCountryContext
Indicates the association between a time zone and the country context within which that time zone is defined or applied.
-
E.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:45 a.m.