Triple
T24565043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nihil Obstat |
E607761
|
entity |
| Predicate | hasMusicalWorkAuthor |
P47024
|
FINISHED |
| Object | Jozef van Wissem |
—
|
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: Jozef van Wissem | Statement: [Nihil Obstat, hasMusicalWorkAuthor, Jozef van Wissem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalWorkAuthor Context triple: [Nihil Obstat, hasMusicalWorkAuthor, Jozef van Wissem]
-
A.
hasMusicalWorkType
Indicates that a musical work is associated with a specific type or category of musical composition.
-
B.
hasMusicalComposer
chosen
Indicates that one entity serves as the musical composer responsible for creating the music associated with another entity.
-
C.
hasMusicalArtistRoleOfCreator
Indicates that the specified musical artist serves as the creator (e.g., composer, originator) of the referenced musical work or content.
-
D.
hasArtistOfNotableWork
Indicates that an entity is associated with the artist who created a notable work related to that entity.
-
E.
hasNotableMusicWork
Indicates that an entity is associated with a significant or well-known musical work, such as a composition, recording, or performance.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8f9d0f881909afc04537c32f76b |
completed | April 30, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.