Triple
T36590098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur A. Ross |
E902644
|
entity |
| Predicate | screenwritingFor |
P48034
|
FINISHED |
| Object | feature films |
—
|
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: feature films | Statement: [Arthur A. Ross, screenwritingFor, feature films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenwritingFor Context triple: [Arthur A. Ross, screenwritingFor, feature films]
-
A.
screenplayDevelopment
Indicates a relationship where a screenplay is being created, refined, or otherwise developed, typically through writing, revising, or collaborative work.
-
B.
screenplayWrittenFor
Indicates that a screenplay was written specifically for a particular film, show, or production.
-
C.
screenwriters
chosen
Indicates that one or more entities are the writers who authored the screenplay or script for a film, show, or similar work.
-
D.
screenwritersContext
Indicates the contextual or collaborative relationship between screenwriters, such as shared projects, influences, or professional associations.
-
E.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:11 p.m.