Triple
T18047882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swear |
E431836
|
entity |
| Predicate | includedInGenreScene |
P81115
|
FINISHED |
| Object | mid-1980s adult contemporary 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: mid-1980s adult contemporary music | Statement: [Swear, includedInGenreScene, mid-1980s adult contemporary music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInGenreScene Context triple: [Swear, includedInGenreScene, mid-1980s adult contemporary music]
-
A.
associatedWithGenreScene
Indicates that an entity is connected or related to a particular genre scene, such as a specific stylistic or cultural subcommunity within a broader genre.
-
B.
includedInGenreCollection
chosen
Indicates that something is a member of, or contained within, a specific genre-based collection.
-
C.
parentGenreScene
Indicates that one scene genre functions as the parent or broader category of another scene genre.
-
D.
coveredInGenre
Indicates that a work or item is associated with, categorized under, or treated within a particular genre.
-
E.
subgenreScene
Indicates that one scene is a more specific subgenre or subtype of another, broader scene category.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4bff39394819080407e1614bd5da9 |
completed | April 19, 2026, 11:43 a.m. |
| PD | Predicate disambiguation | batch_69e3f908da508190a088aa837ea5b7af |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:25 a.m.