Triple
T8315827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KatzSmith Productions |
E194703
|
entity |
| Predicate | workAdaptationType |
P2375
|
FINISHED |
| Object | literary adaptations |
—
|
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: literary adaptations | Statement: [KatzSmith Productions, workAdaptationType, literary adaptations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAdaptationType Context triple: [KatzSmith Productions, workAdaptationType, literary adaptations]
-
A.
basedOnWorkAdaptedTo
Indicates that one work is derived from and adapted based on the content, story, or elements of another pre-existing work.
-
B.
hasWorkAdaptation
Indicates that an entity has a modified, adjusted, or alternative form specifically adapted for use in a work or professional context.
-
C.
hasWorkAdaptedBy
Indicates that one work has been transformed or re-created into another work, such as through adaptation into a different medium or format.
-
D.
adaptationType
chosen
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
E.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f540b2081908ccb1b2ed040c74e |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.