Triple
T28727487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovecraft, Massachusetts |
E730263
|
entity |
| Predicate | primaryWorkSettingOf |
P58315
|
FINISHED |
| Object | Locke & Key |
—
|
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: Locke & Key | Statement: [Lovecraft, Massachusetts, primaryWorkSettingOf, Locke & Key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWorkSettingOf Context triple: [Lovecraft, Massachusetts, primaryWorkSettingOf, Locke & Key]
-
A.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
-
B.
primaryWork
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
C.
residesInWork
Indicates that a person or entity lives or is based within the location, setting, or environment defined by a particular work (such as a book, film, or other creative piece).
-
D.
workSetting
chosen
Indicates the environment, context, or conditions in which the work or activity is carried out.
-
E.
workedPrimarilyIn
Indicates that an entity carried out the majority of its work, activity, or career within a particular field, location, or context.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
Created at: April 28, 2026, 5:56 a.m.