Triple
T25511729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Benson |
E639399
|
entity |
| Predicate | scriptStatusAtStart |
P89191
|
FINISHED |
| Object | overdue 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: overdue screenplay | Statement: [Richard Benson, scriptStatusAtStart, overdue screenplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptStatusAtStart Context triple: [Richard Benson, scriptStatusAtStart, overdue screenplay]
-
A.
hasScriptStatus
Indicates that an entity has a particular script-related state or condition, such as whether a script is present, active, or in a given status.
-
B.
initialStatus
chosen
Indicates the original or starting state assigned to an entity before any changes or updates occur.
-
C.
hasSiteStatusAtStart
Indicates that an entity possesses a particular site status at the beginning of a specified period or event.
-
D.
scriptStageOf
Indicates that something represents a particular stage or step within the overall structure or progression of a script.
-
E.
scriptStage
Indicates the specific phase or step within a scripted process, workflow, or narrative that an entity is currently in or associated with.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80b05ac8190a4a0cd75e8717917 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 2:49 p.m.