Triple
T29010360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A.S.C.H.–S.C.H.A. (Lettres dansantes) |
E736546
|
entity |
| Predicate | usesMusicalCipher |
P177137
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [A.S.C.H.–S.C.H.A. (Lettres dansantes), usesMusicalCipher, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMusicalCipher Context triple: [A.S.C.H.–S.C.H.A. (Lettres dansantes), usesMusicalCipher, yes]
-
A.
usesMusicalSystem
Indicates that one entity employs or operates according to a particular musical system, framework, or set of musical rules.
-
B.
usesMusicalElement
Indicates that one entity employs or incorporates a particular musical element (such as rhythm, melody, harmony, or timbre) in its composition, performance, or structure.
-
C.
hasMusical
Indicates that one entity features, includes, or is associated with a musical work, performance, or musical component.
-
D.
hasMusicalNumberIn
Indicates that a musical number (song or performance) appears within or is featured in a specific work, scene, or production.
-
E.
usesClef
Indicates that one entity employs or applies a particular clef in a musical notation context.
- F. None of above. chosen
Provenance (4 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 28, 2026, 9:41 a.m.