Triple
T9742376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spotlight |
E236216
|
entity |
| Predicate | typicalAudienceReception |
P86061
|
FINISHED |
| Object | highly anticipated titles |
—
|
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: highly anticipated titles | Statement: [Spotlight, typicalAudienceReception, highly anticipated titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAudienceReception Context triple: [Spotlight, typicalAudienceReception, highly anticipated titles]
-
A.
typicalAudienceResponse
chosen
Indicates the usual or expected reaction, behavior, or feedback that an audience has in response to a given work, event, or communication.
-
B.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
D.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
E.
audienceScale
Indicates the relative size or reach of the audience associated with an entity, event, or communication.
- 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_69ca84d3e24481908a476e2231123cf9 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9f2cb7008190a829a03114d6c704 |
completed | April 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69cd03cc128c81908b84ef224f858b4e |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:23 p.m.