Triple
T37357036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allemanda |
E927481
|
entity |
| Predicate | commonStyle |
P46850
|
FINISHED |
| Object | continuous semiquaver motion |
—
|
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: continuous semiquaver motion | Statement: [Allemanda, commonStyle, continuous semiquaver motion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonStyle Context triple: [Allemanda, commonStyle, continuous semiquaver motion]
-
A.
uniformStyle
chosen
Indicates that the related entities share the same or a consistent style, pattern, or formatting.
-
B.
typicalContentStyle
Indicates the usual or characteristic manner, format, or stylistic approach in which content associated with an entity is presented.
-
C.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
-
D.
compositionStyle
Indicates the characteristic manner or approach in which something is composed, such as its structural, aesthetic, or stylistic conventions.
-
E.
typicalVisualStyle
Indicates the characteristic or commonly observed visual appearance or aesthetic style associated with an 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.