Triple
T31116687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 6 in C major "Little C major" |
E793107
|
entity |
| Predicate | relativeScale |
P207358
|
FINISHED |
| Object | A 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: A minor | Statement: [Symphony No. 6 in C major "Little C major", relativeScale, A minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeScale Context triple: [Symphony No. 6 in C major "Little C major", relativeScale, A minor]
-
A.
relatedScale
Indicates that two entities are connected through a common or comparable scale, measurement, or gradation system.
-
B.
similarScaleTo
Indicates that two entities have comparable magnitude, size, or extent along a given dimension or measurement scale.
-
C.
relativeLength
Indicates a comparative relationship between entities based on how long they are relative to one another.
-
D.
associatedScale
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
-
E.
scaleRelation
Indicates a relationship where one quantity, object, or representation is proportionally larger or smaller than another according to a specific scale or factor.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:04 p.m.