Triple
T16856256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Concerto |
E409791
|
entity |
| Predicate | predecessorGenre |
P125250
|
FINISHED |
| Object | harpsichord concerto |
—
|
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: harpsichord concerto | Statement: [Piano Concerto, predecessorGenre, harpsichord concerto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorGenre Context triple: [Piano Concerto, predecessorGenre, harpsichord concerto]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorCulture
Indicates that one culture historically preceded and contributed to the development of another culture.
-
C.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
D.
predecessorSystem
Indicates that one system existed or was in use before and was replaced or superseded by another system.
-
E.
previousGenus
Indicates that one genus was previously used as the taxonomic genus for an organism before being reclassified to another genus.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37d69a08190af18b421066f44f1 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:24 a.m.