Triple
T36331265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreaming Frankenstein and Collected Poems |
E894653
|
entity |
| Predicate | isPrimaryWorkOf |
P40956
|
FINISHED |
| Object | Liz Lochhead |
—
|
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: Liz Lochhead | Statement: [Dreaming Frankenstein and Collected Poems, isPrimaryWorkOf, Liz Lochhead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryWorkOf Context triple: [Dreaming Frankenstein and Collected Poems, isPrimaryWorkOf, Liz Lochhead]
-
A.
primaryWork
chosen
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
B.
isAWorkBy
Indicates that one entity is a creative work that has been produced or authored by another entity.
-
C.
isPrimary
Indicates that one entity holds the main, leading, or most important role or status in relation to another entity or within a given context.
-
D.
workedPrimarilyOn
Indicates that an entity devoted the majority of its work, effort, or activity to a particular project, field, or subject.
-
E.
isWork
Indicates that an entity functions as a work (such as a creation, product, or task) in relation 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: May 3, 2026, 4:09 p.m.