Triple
T31228301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeolian Hall |
E796204
|
entity |
| Predicate | hostedComposer |
P147604
|
FINISHED |
| Object | George Gershwin |
—
|
NE NERFINISHED |
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: George Gershwin | Statement: [Aeolian Hall, hostedComposer, George Gershwin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedComposer Context triple: [Aeolian Hall, hostedComposer, George Gershwin]
-
A.
composer
Indicates that one entity is the creator or writer of a musical work associated with another entity.
-
B.
studioHost
Indicates that one entity serves as the host or presenter within a studio setting for another entity or program.
-
C.
hostedEnvironment
Indicates that one entity provides the runtime or operational environment in which another entity is deployed, executed, or made available.
-
D.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
E.
composerOn
chosen
Indicates that one entity serves as the composer or creator of a musical or audio work 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 9:10 p.m.