Triple
T17088100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skudeneshavn |
E414652
|
entity |
| Predicate | SkudefestivalenIs |
P96461
|
FINISHED |
| Object | annual summer festival |
—
|
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: annual summer festival | Statement: [Skudeneshavn, SkudefestivalenIs, annual summer festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SkudefestivalenIs Context triple: [Skudeneshavn, SkudefestivalenIs, annual summer festival]
-
A.
Pfifferdaj
Indicates a relationship or action associated with the Pfifferdaj festival or event, such as participation in, organization of, or occurrence during that festival.
-
B.
Sneekweek
Indicates participation in or association with the Dutch student sailing and water sports event known as Sneekweek.
-
C.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
-
D.
festivalDay
Indicates that a given day is designated as a festival or celebration day within a particular context or calendar.
-
E.
festivalFeature
chosen
Indicates that a festival includes or showcases a particular element, activity, or attraction as one of its features.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe92e488190b947287a968086d5 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.