Triple
T9998047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jon Spaihts |
E197253
|
entity |
| Predicate | screenplayGenreSpecialty |
P21380
|
FINISHED |
| Object | science fiction |
—
|
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: science fiction | Statement: [Jon Spaihts, screenplayGenreSpecialty, science fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenplayGenreSpecialty Context triple: [Jon Spaihts, screenplayGenreSpecialty, science fiction]
-
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.
genreSpecialty
chosen
Indicates that an entity specializes in or is particularly associated with a specific genre.
-
D.
screenplayAwardedBy
Indicates that a screenplay has received an award from a particular awarding body or organization.
-
E.
theatricalGenre
Indicates the specific theatrical genre or style to which a performance, play, or production belongs.
- 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_69ca82f3b61c81908ecc2c1c96dbc2e4 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdcc8aa1a881909879a694496f11a5 |
completed | April 2, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69cd1da07db88190945bcdab3ca82e71 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.