Triple
T2809034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cello Suites |
E54122
|
entity |
| Predicate | keyOfSuite1 |
P43345
|
FINISHED |
| Object | G 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: G major | Statement: [Cello Suites, keyOfSuite1, G major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyOfSuite1 Context triple: [Cello Suites, keyOfSuite1, G major]
-
A.
testSuite
Indicates that one entity is a collection or grouping of tests designed to be executed together, typically to validate behavior or functionality.
-
B.
keyType
Indicates the classification or category of a key in relation to how it is used or defined within a system or context.
-
C.
keyRite
Indicates that an entity performs or is associated with a ritual, ceremony, or formal procedure involving a key (literal or symbolic).
-
D.
keySection
Indicates that one section is the primary or most important part within a larger structure or document.
-
E.
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.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde3165b48190a43be5e6ad23deca |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 9:59 p.m.