Triple
T31945666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H 81 |
E815644
|
entity |
| Predicate | associatedGenreOfReferredWork |
P146635
|
FINISHED |
| Object | art song |
—
|
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: art song | Statement: [H 81, associatedGenreOfReferredWork, art song]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedGenreOfReferredWork Context triple: [H 81, associatedGenreOfReferredWork, art song]
-
A.
referencedInGenre
Indicates that one entity is mentioned, cited, or otherwise referred to within the context of a particular genre.
-
B.
hasGenreOfWorkItAppearsIn
chosen
Indicates that an entity is associated with the genre of the work in which it appears.
-
C.
genreRelation
Indicates a relationship where one entity is categorized as having, belonging to, or being associated with a particular genre defined by another entity.
-
D.
associatedWithGenreElement
Indicates that something has a connection or linkage to a specific genre-related element (such as a motif, convention, or stylistic feature).
-
E.
genreAssociatedWith
Indicates a relationship where a work, item, or entity is linked to or categorized under a particular genre.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:06 a.m.