Triple
T26561636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terschelling |
E666257
|
entity |
| Predicate | OerolFestivalType |
P91710
|
FINISHED |
| Object | theatre and landscape arts 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: theatre and landscape arts festival | Statement: [Terschelling, OerolFestivalType, theatre and landscape arts festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OerolFestivalType Context triple: [Terschelling, OerolFestivalType, theatre and landscape arts festival]
-
A.
operaFestivalVenue
Indicates that a venue is the location where an opera festival is held.
-
B.
theatreType
Indicates the specific category or kind of theatre associated with an entity, such as its format, style, or operational model.
-
C.
festivalTypeHosted
chosen
Indicates that a particular location or organizer hosts festivals of a specified type.
-
D.
festivalSystem
Indicates a relationship where an entity is part of, managed by, or associated with a festival-related organizational or operational system.
-
E.
festivalOrganiser
Indicates that one entity is responsible for planning, coordinating, or managing a festival for another entity or context.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6146c6e188190aa022ef2b9ee1774 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:53 a.m.