Triple
T11231436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Heermann |
E265829
|
entity |
| Predicate | workUsedIn |
P10343
|
FINISHED |
| Object | Protestant church 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: Protestant church music | Statement: [Johann Heermann, workUsedIn, Protestant church music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workUsedIn Context triple: [Johann Heermann, workUsedIn, Protestant church music]
-
A.
workUsedAs
Indicates that one work is employed or utilized in the creation, performance, or presentation of another work.
-
B.
usedInWork
chosen
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
-
E.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9026e1c81909456ac946bbba972 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.