Triple
T10361430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edgar Linton |
E244141
|
entity |
| Predicate | narrativelyFunctionAs |
P80898
|
FINISHED |
| Object | Foil to Heathcliff |
—
|
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: Foil to Heathcliff | Statement: [Edgar Linton, narrativelyFunctionAs, Foil to Heathcliff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativelyFunctionAs Context triple: [Edgar Linton, narrativelyFunctionAs, Foil to Heathcliff]
-
A.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
B.
narrativeStrategy
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
C.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
D.
narrativePurpose
chosen
Indicates the role or function that something serves within the structure or progression of a narrative.
-
E.
narrativeCharacteristic
Indicates that one entity serves as a descriptive or defining narrative feature or quality of 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e96209548190957368ee8c6a9ec3 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:59 a.m.