Triple
T24552816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wackiest Ship in the Army |
E607417
|
entity |
| Predicate | screenplayAdaptationForTVBy |
P23410
|
FINISHED |
| Object | Danny Arnold |
—
|
NE NERFINISHED |
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: Danny Arnold | Statement: [The Wackiest Ship in the Army, screenplayAdaptationForTVBy, Danny Arnold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayAdaptationForTVBy Context triple: [The Wackiest Ship in the Army, screenplayAdaptationForTVBy, Danny Arnold]
-
A.
screenplayWrittenFor
Indicates that a screenplay was written specifically for a particular film, show, or production.
-
B.
screenplayBy
Indicates that a film, television show, or similar work was written or scripted by a particular person or group.
-
C.
screenWriterAdaptationBy
chosen
Indicates that a person served as the screenwriter responsible for adapting an existing work into a screenplay.
-
D.
screenplayDevelopment
Indicates a relationship where a screenplay is being created, refined, or otherwise developed, typically through writing, revising, or collaborative work.
-
E.
screenplayForDirector
Indicates that a screenplay is written or created specifically for a particular director to direct.
- 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_69e2c4cae1b88190825e88d5ce8aa61e |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a8cf1ef88190977da0fb79796616 |
completed | April 30, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:27 a.m.