Triple
T28631687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Swedish Opera House |
E724655
|
entity |
| Predicate | hasArtisticResident |
P98905
|
FINISHED |
| Object | Royal Swedish Orchestra |
—
|
NE NERFINISHED |
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: Royal Swedish Orchestra | Statement: [Royal Swedish Opera House, hasArtisticResident, Royal Swedish Orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArtisticResident Context triple: [Royal Swedish Opera House, hasArtisticResident, Royal Swedish Orchestra]
-
A.
hasResidentArtist
chosen
Indicates that one entity serves as the resident artist associated with or based at another entity.
-
B.
artistResidence
Indicates that a given location is the place where an artist lives or is based.
-
C.
hasArtisticAdvisor
Indicates that one entity serves as an artistic advisor, providing artistic guidance or counsel, to another entity.
-
D.
hasComposerInResidence
Indicates that an organization or institution has officially appointed a specific composer to serve in a resident or ongoing compositional role.
-
E.
hasArtisticAssociationWith
Indicates a relationship in which two entities are connected through shared, collaborative, or thematically related artistic work or influence.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:37 a.m.