Triple
T16721610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malice |
E406360
|
entity |
| Predicate | screenplayFeature |
P124377
|
FINISHED |
| Object | courtroom scenes |
—
|
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: courtroom scenes | Statement: [Malice, screenplayFeature, courtroom scenes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayFeature Context triple: [Malice, screenplayFeature, courtroom scenes]
-
A.
screenplayType
Indicates the specific category or format of a screenplay associated with a work or production.
-
B.
screenplayRecord
Indicates that there exists a record or documentation associated with a particular screenplay, capturing information about its creation, version, or related details.
-
C.
screenplayDevelopedBy
Indicates that a screenplay was created, written, or otherwise developed by a particular person or organization.
-
D.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
-
E.
screenplayForDirector
Indicates that a screenplay is written or created specifically for a particular director to direct.
- F. None of above. chosen
Provenance (4 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38743750c81908a980372ad8f1a6a |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.