Triple
T33527788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earnshaw family |
E858688
|
entity |
| Predicate | framedByNarrator |
P49701
|
FINISHED |
| Object | Lockwood |
—
|
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: Lockwood | Statement: [Earnshaw family, framedByNarrator, Lockwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: framedByNarrator Context triple: [Earnshaw family, framedByNarrator, Lockwood]
-
A.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
B.
fictionalNarrator
Indicates that one entity serves as the narrator or storytelling voice within a fictional work that features the other entity.
-
C.
describedByNarrator
chosen
Indicates that something is presented or explained through the perspective or voice of a narrator.
-
D.
narratorIn
Indicates that one entity serves as the narrator or storytelling voice within the context of another entity (such as a work, scene, or narrative segment).
-
E.
narratorBasedOn
Indicates that a narrative’s narrator is modeled on, inspired by, or derived from a particular real or fictional 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:39 a.m.