Triple
T1664824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleep (1963 film) |
E35985
|
entity |
| Predicate | hasAudienceReaction |
P15291
|
FINISHED |
| Object | controversial for length |
—
|
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: controversial for length | Statement: [Sleep (1963 film), hasAudienceReaction, controversial for length]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAudienceReaction Context triple: [Sleep (1963 film), hasAudienceReaction, controversial for length]
-
A.
hasAudienceReception
chosen
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
B.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
C.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
D.
hasUserAttitude
Indicates that one entity holds a particular attitude, opinion, or evaluative stance toward another entity or subject.
-
E.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
- 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa994f92b0819084ee2f6a672334b9 |
completed | March 6, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69a907d2475c8190b7ec7dccd3335eb1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.