Triple
T10274376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Capital of Culture 2013 |
E240924
|
entity |
| Predicate | includesActivityType |
P20949
|
FINISHED |
| Object | cultural festivals |
—
|
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: cultural festivals | Statement: [European Capital of Culture 2013, includesActivityType, cultural festivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesActivityType Context triple: [European Capital of Culture 2013, includesActivityType, cultural festivals]
-
A.
hasActivityType
chosen
Indicates the specific kind or category of activity associated with an entity or event.
-
B.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
C.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
permittedActivity
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
-
E.
participationIncludes
Indicates that a broader participation instance encompasses or contains a more specific participation instance as part of it.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d28a9c508190824867c04e8dcbe7 |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:36 a.m.