Triple
T23455376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alison Lockhart |
E567906
|
entity |
| Predicate | centralThemeInStoryline |
P6627
|
FINISHED |
| Object | infidelity |
—
|
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: infidelity | Statement: [Alison Lockhart, centralThemeInStoryline, infidelity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralThemeInStoryline Context triple: [Alison Lockhart, centralThemeInStoryline, infidelity]
-
A.
primaryStoryThemes
Indicates the main recurring ideas or motifs that characterize and unify a story’s narrative.
-
B.
centralThemeConnection
Indicates a relationship where one element serves as the primary or unifying theme that conceptually links or organizes the other element(s).
-
C.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
-
D.
centralThemeContext
Indicates that one concept serves as the main thematic focus within the situational, narrative, or discourse context defined by another.
-
E.
hasCentralTheme
chosen
Indicates that one entity serves as the primary or dominant theme or subject matter 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_69e2458b4c888190b1d7998f9862a558 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a696e6c48190a7159292cfe3362f |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:53 p.m.