Triple
T32429334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Passing Show of 1923 |
E828673
|
entity |
| Predicate | hasComponentGenre |
P206277
|
FINISHED |
| Object | music |
—
|
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: music | Statement: [The Passing Show of 1923, hasComponentGenre, music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentGenre Context triple: [The Passing Show of 1923, hasComponentGenre, music]
-
A.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
-
B.
hasUseGenre
Indicates that something (such as a work, product, or item) is associated with or categorized under a particular genre for its use or purpose.
-
C.
hasGenreFeature
Indicates that something possesses a characteristic, element, or trait associated with a particular genre.
-
D.
hasGenreFunction
Indicates that something serves a particular genre-related role or function within a classification or organizational context.
-
E.
hasGenreAsSetting
Indicates that a work’s setting is characterized by, or takes place within, a particular genre.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:54 a.m.