Triple
T38599286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C major |
E934164
|
entity |
| Predicate | isNotatedWith |
P133304
|
FINISHED |
| Object | no sharps |
—
|
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: no sharps | Statement: [C major, isNotatedWith, no sharps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotatedWith Context triple: [C major, isNotatedWith, no sharps]
-
A.
isNotatedFor
Indicates that something (such as a piece of music or performance) is written or represented in a specific notation system or format.
-
B.
appearsInNotation
chosen
Indicates that one entity is represented, referenced, or depicted within the formal notation or symbolic system associated with another entity.
-
C.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
D.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
E.
formalNotation
Indicates that one entity is the formal symbolic or notational representation of another entity or concept.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.