Triple
T11581906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contrapunctus III |
E274646
|
entity |
| Predicate | basedOnThemeOf |
P83682
|
FINISHED |
| Object | principal Art of Fugue subject |
—
|
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: principal Art of Fugue subject | Statement: [Contrapunctus III, basedOnThemeOf, principal Art of Fugue subject]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnThemeOf Context triple: [Contrapunctus III, basedOnThemeOf, principal Art of Fugue subject]
-
A.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
C.
usesThemeFrom
chosen
Indicates that one work incorporates, references, or is based on the thematic material of another work.
-
D.
themedAs
Indicates that something is characterized, styled, or organized according to a particular theme or motif.
-
E.
followsTheme
Indicates that one entity adheres to, is guided by, or is structured according to the theme established by 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8904c51b881909e7be84c6f3de79f |
completed | April 10, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.