Triple
T20268831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreams So Real |
E499037
|
entity |
| Predicate | hasComposerFocus |
P132759
|
FINISHED |
| Object | jazz compositions |
—
|
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: jazz compositions | Statement: [Dreams So Real, hasComposerFocus, jazz compositions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComposerFocus Context triple: [Dreams So Real, hasComposerFocus, jazz compositions]
-
A.
hasCompositionalFocus
chosen
Indicates that one entity is the primary subject or focal element within the compositional structure of another entity.
-
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.
hasActingFocus
Indicates that an entity is the primary performer or focal agent carrying out an action in a given context.
-
E.
hasComposerDeathContext
Indicates the contextual circumstances or setting associated with a composer's death.
- 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e675dc8e708190b840d687f134c9e8 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:42 p.m.