Triple
T25415521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Passionate Witch |
E636821
|
entity |
| Predicate | adaptationTypeOf |
P2375
|
FINISHED |
| Object | I Married a Witch |
—
|
NE NERFINISHED |
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: I Married a Witch | Statement: [The Passionate Witch, adaptationTypeOf, I Married a Witch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationTypeOf Context triple: [The Passionate Witch, adaptationTypeOf, I Married a Witch]
-
A.
adaptationType
chosen
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
B.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
C.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
D.
adaptationSubject
Indicates that one entity serves as the source or subject matter that is adapted into another work or form.
-
E.
adaptationDetail
Indicates that additional information is provided about how something has been adapted or modified from its original form.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5b0119ee0819088c4985bd7862cab |
completed | May 2, 2026, 8:04 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:55 p.m.