Triple
T38174682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon per tonos |
E1000172
|
entity |
| Predicate | modulatesTo |
P34126
|
FINISHED |
| Object | D minor |
—
|
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: D minor | Statement: [Canon per tonos, modulatesTo, D minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modulatesTo Context triple: [Canon per tonos, modulatesTo, D minor]
-
A.
modulates
chosen
Indicates that one entity adjusts, regulates, or alters the intensity, frequency, or effect of another entity or process.
-
B.
usesModulation
Indicates that one entity applies or employs a particular modulation method or scheme in relation to another entity or process.
-
C.
definesModulation
Indicates that one entity specifies or determines how another entity is modulated or altered in its behavior, intensity, or effect.
-
D.
regulatesThrough
Indicates that one entity exerts control or influence over another by means of an intermediate mechanism, pathway, or process.
-
E.
regulatesWith
Indicates that one entity controls, modulates, or influences the activity, state, or behavior of another entity through some regulatory mechanism or interaction.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.