Triple
T10963748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drunk on You |
E259042
|
entity |
| Predicate | isInGenreScene |
P22737
|
FINISHED |
| Object | bro-country era |
—
|
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: bro-country era | Statement: [Drunk on You, isInGenreScene, bro-country era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInGenreScene Context triple: [Drunk on You, isInGenreScene, bro-country era]
-
A.
associatedWithGenreScene
chosen
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.
containsScene
Indicates that one entity (typically a media item or narrative work) includes or features a particular scene as part of its content.
-
C.
hasGenreScope
Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
-
D.
containsGenreElement
Indicates that something includes or incorporates an element characteristic of a particular genre.
-
E.
performedInSceneType
Indicates that an action or event was carried out within a scene of a specified type or 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77147f7108190a3b68ba1dd1c130e |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.