Triple
T30399545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Köln Concert |
E773311
|
entity |
| Predicate | hasKeyCharacteristics |
P274
|
FINISHED |
| Object | lyrical improvisation |
—
|
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: lyrical improvisation | Statement: [The Köln Concert, hasKeyCharacteristics, lyrical improvisation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyCharacteristics Context triple: [The Köln Concert, hasKeyCharacteristics, lyrical improvisation]
-
A.
hasKeyInformation
Indicates that an entity possesses or contains essential or critical information relevant to another entity, context, or task.
-
B.
hasTradeCharacteristic
Indicates that an entity possesses a specific trade-related attribute, quality, or feature.
-
C.
hasRuleCharacteristic
Indicates that something possesses a specific property, feature, or attribute related to a rule or set of rules.
-
D.
hasCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
-
E.
hasStyleCharacteristics
Indicates that one entity exhibits or embodies the stylistic features, traits, or qualities associated with another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 8:03 p.m.