Triple
T31007320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amanda Posey |
E790103
|
entity |
| Predicate | basedOnAdaptations |
P96392
|
FINISHED |
| Object | literary works |
—
|
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 works | Statement: [Amanda Posey, basedOnAdaptations, literary works]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnAdaptations Context triple: [Amanda Posey, basedOnAdaptations, literary works]
-
A.
basedOnAdaptationsOf
Indicates that something is derived from or created using one or more prior adaptations of an original work, rather than directly from the original source.
-
B.
basedOnAdaptationWorkedOn
chosen
Indicates that something is derived from or created based on an adaptation that a particular agent worked on.
-
C.
hasAdaptationsIn
Indicates that something possesses or exhibits adaptations within a particular context, environment, or domain.
-
D.
typicalAdaptations
Indicates the characteristic adaptations or traits that are commonly associated with or typical for an entity in a given context.
-
E.
overseesAdaptationsOf
Indicates that one entity has responsibility for supervising, managing, or directing the adaptations or modifications made to another entity.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: April 29, 2026, 8:57 p.m.