Triple
T27781793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big White |
E699350
|
entity |
| Predicate | hasScreenplayType |
P30807
|
FINISHED |
| Object | original screenplay |
—
|
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: original screenplay | Statement: [The Big White, hasScreenplayType, original screenplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreenplayType Context triple: [The Big White, hasScreenplayType, original screenplay]
-
A.
screenplayType
chosen
Indicates the specific category or format of a screenplay associated with a work or production.
-
B.
hasScreenplayStyle
Indicates that an entity is associated with or characterized by a particular style or manner of screenplay writing.
-
C.
screenplayWrittenFor
Indicates that a screenplay was written specifically for a particular film, show, or production.
-
D.
wroteScreenplaysFor
Indicates that one entity is the author or writer of screenplays created for another entity, such as a film, series, or production.
-
E.
hasScreenwriter
Indicates that a creative work is associated with the person or entity who wrote its screenplay or script.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 27, 2026, 5:10 p.m.