Triple
T31477086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chopin Festival |
E803023
|
entity |
| Predicate | hasInstrumentFocus |
P155464
|
FINISHED |
| Object | piano |
—
|
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: piano | Statement: [Chopin Festival, hasInstrumentFocus, piano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstrumentFocus Context triple: [Chopin Festival, hasInstrumentFocus, piano]
-
A.
hasPrimaryInstrumentFocus
chosen
Indicates that an entity’s main emphasis or specialization is centered on a particular instrument.
-
B.
hasProgramFocus
Indicates that an entity (such as a program or initiative) is oriented around or primarily concerned with a particular thematic area, topic, or objective.
-
C.
hasGlobalFocus
Indicates that something is oriented toward, concerned with, or applicable to worldwide or international scope rather than a local or regional one.
-
D.
hasVisualFocus
Indicates that one entity is currently directing its visual attention or gaze toward another entity.
-
E.
hasCharacterFocus
Indicates that a work, scene, or segment centers primarily on a particular character’s experiences, perspective, or development.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: April 30, 2026, 9:29 p.m.