Triple
T9913498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portnoy's Complaint (film) |
E185804
|
entity |
| Predicate | sourceWorkDescribedAs |
P44666
|
FINISHED |
| Object | controversial |
—
|
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 | Statement: [Portnoy's Complaint (film), sourceWorkDescribedAs, controversial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceWorkDescribedAs Context triple: [Portnoy's Complaint (film), sourceWorkDescribedAs, controversial]
-
A.
workDescribedIn
Indicates that a work (such as a publication or document) provides a description or account of the referenced entity.
-
B.
sourceWorkFirstPerformed
Indicates the original performance event or context in which a work was first publicly performed.
-
C.
workDescribedAs
chosen
Indicates that one entity’s work, project, or output is characterized, labeled, or referred to by a particular description, title, or phrase.
-
D.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
E.
subjectOfWork
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
- 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_69ca829b45f481909040f7b99a1976ed |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cdb53a300481909d917e487d8aab56 |
completed | April 2, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:41 p.m.