Triple
T30728320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billy Howle |
E782342
|
entity |
| Predicate | basedOnWorkTypeOftenAppearsIn |
P195141
|
FINISHED |
| Object | literary adaptation |
—
|
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 adaptation | Statement: [Billy Howle, basedOnWorkTypeOftenAppearsIn, literary adaptation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnWorkTypeOftenAppearsIn Context triple: [Billy Howle, basedOnWorkTypeOftenAppearsIn, literary adaptation]
-
A.
associatedWorkType
Indicates the type or category of work with which an entity is associated (e.g., publication, artwork, performance).
-
B.
basedOnWorkAppearsIn
Indicates that one work is derived from or informed by another work in which it appears or is featured.
-
C.
usedInWorkBy
Indicates that something (such as a method, material, or concept) is employed or incorporated within a work created by a particular agent or author.
-
D.
basedOnWorkCollection
Indicates that something is derived from, adapted from, or otherwise created using a particular collection of works as its source or foundation.
-
E.
typeOfWork
Indicates the kind or category of work associated with or performed by an entity.
- F. None of above. chosen
Provenance (4 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
| PDg | Predicate description generation | batch_69fda945e1e08190bf923fcd4d2c548a |
completed | May 8, 2026, 9:13 a.m. |
Created at: April 29, 2026, 8:37 p.m.