Triple
T295421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katrina Van Tassel |
E6081
|
entity |
| Predicate | narrativeFunction |
P7328
|
FINISHED |
| Object | love interest |
—
|
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: love interest | Statement: [Katrina Van Tassel, narrativeFunction, love interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeFunction Context triple: [Katrina Van Tassel, narrativeFunction, love interest]
-
A.
storyFunction
chosen
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
-
B.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
C.
narrativeStyle
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
D.
containsNarrativeOf
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
E.
storyBy
Indicates that one entity is the creator or author of the story associated with 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2e9e273f88190ac5355d1310376ed |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e9368894819093eeae4347dfcc5a |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.