Triple
T9277308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FestspielOrchester Göttingen |
E222980
|
entity |
| Predicate | roleAtFestival |
P35474
|
FINISHED |
| Object | resident orchestra |
—
|
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: resident orchestra | Statement: [FestspielOrchester Göttingen, roleAtFestival, resident orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtFestival Context triple: [FestspielOrchester Göttingen, roleAtFestival, resident orchestra]
-
A.
operatesFestival
Indicates that one entity manages and runs the organization or execution of a festival for another entity or in a particular context.
-
B.
positionInFestival
chosen
Indicates the specific role, slot, or placement an entity holds within the structure or schedule of a festival.
-
C.
determinesFestival
Indicates that one entity decides, defines, or selects which festival is applicable or will occur for another entity or context.
-
D.
eventRole
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
E.
peerFestival
Indicates that two festivals are considered peers, sharing a comparable status, scale, or role within a given 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07c95a98819098528b7ada37ddc1 |
completed | April 1, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.