Triple
T11916817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grote Zaal |
E283544
|
entity |
| Predicate | secondaryGenreFocus |
P71102
|
FINISHED |
| Object | contemporary music |
—
|
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: contemporary music | Statement: [Grote Zaal, secondaryGenreFocus, contemporary music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryGenreFocus Context triple: [Grote Zaal, secondaryGenreFocus, contemporary music]
-
A.
secondaryGenre
chosen
Indicates that an entity (such as a work or item) has an additional, non-primary genre classification associated with it.
-
B.
subgenre
Indicates that one genre is a more specific, subordinate category within a broader parent genre.
-
C.
secondaryClassification
Indicates a secondary or additional categorization assigned to an entity beyond its primary classification.
-
D.
secondaryAudience
Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
-
E.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8deb14881909b65a1f159aec65f |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.