Triple
T11464496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prestige pictures |
E271745
|
entity |
| Predicate | typicalTargetAudience |
P10804
|
FINISHED |
| Object | adult viewers |
—
|
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: adult viewers | Statement: [Prestige pictures, typicalTargetAudience, adult viewers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTargetAudience Context triple: [Prestige pictures, typicalTargetAudience, adult viewers]
-
A.
typicalAudience
chosen
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
B.
typicalAudienceResponse
Indicates the usual or expected reaction, behavior, or feedback that an audience has in response to a given work, event, or communication.
-
C.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
D.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
-
E.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f488248190b9f603cd31c72174 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.