Triple
T35660454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaches Ain't Ready |
E1030417
|
entity |
| Predicate | promotesGenreElements |
P70290
|
FINISHED |
| Object | action |
—
|
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: action | Statement: [Beaches Ain't Ready, promotesGenreElements, action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotesGenreElements Context triple: [Beaches Ain't Ready, promotesGenreElements, action]
-
A.
promotesGenre
chosen
Indicates that one entity actively supports, advertises, or increases the visibility of a particular genre.
-
B.
promotedGenre
Indicates that a particular genre is being actively highlighted, advertised, or given preferential visibility or status.
-
C.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
D.
supportedGenre
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
-
E.
servedGenre
Indicates that a service, venue, or provider offers or specializes in a particular genre (such as a style, category, or type of content).
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:05 p.m.