Triple
T736556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaunas |
E14945
|
entity |
| Predicate | wasEuropeanCapitalOfCultureInYear |
P19408
|
FINISHED |
| Object | 2022 |
—
|
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: 2022 | Statement: [Kaunas, wasEuropeanCapitalOfCultureInYear, 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEuropeanCapitalOfCultureInYear Context triple: [Kaunas, wasEuropeanCapitalOfCultureInYear, 2022]
-
A.
UNESCOCreativeCityNetworkMemberSince
Indicates that a city has been part of the UNESCO Creative Cities Network starting from a specified date or year.
-
B.
hasCulturalCentre
Indicates that one entity possesses, hosts, or contains a cultural centre associated with it.
-
C.
yearOfEurovisionParticipation
Indicates the year in which an entity participated in the Eurovision Song Contest.
-
D.
isCulturalCenterFor
Indicates that one entity serves as a primary hub or focal point for the cultural activities, heritage, or identity of another entity.
-
E.
isCulturalCenter
Indicates that an entity serves as a primary hub or focal point for the cultural activities, expressions, and institutions of a community or region.
- 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_69a4934d9930819099eed80096b0597d |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fc734c81908fbd36386d5746d6 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a64957ec81909fe2e2dbffd80ed3 |
completed | March 1, 2026, 8:49 p.m. |
Created at: March 1, 2026, 7:37 p.m.