Triple
T32854728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D 950 |
E840344
|
entity |
| Predicate | endingKey |
P157607
|
FINISHED |
| Object | B-flat major |
—
|
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: B-flat major | Statement: [D 950, endingKey, B-flat major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endingKey Context triple: [D 950, endingKey, B-flat major]
-
A.
endsInKey
chosen
Indicates that an event, sequence, or musical piece concludes in a specified key.
-
B.
inKey
Indicates that something is contained within, associated with, or represented by a particular key in a key-based structure (such as a map, dictionary, or key-value store).
-
C.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
D.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
E.
keyHolding
Indicates that one entity possesses and controls access to a key associated with another entity or resource.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce7d0c2481908adf89dce746b0fd |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:17 a.m.