Triple
T25223819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pam |
E632036
|
entity |
| Predicate | narrativeThemeOfWork |
P161636
|
FINISHED |
| Object | betrayal |
—
|
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: betrayal | Statement: [Pam, narrativeThemeOfWork, betrayal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeThemeOfWork Context triple: [Pam, narrativeThemeOfWork, betrayal]
-
A.
narrativeFocusOfWork
Indicates that a particular element (such as a character, event, or theme) is the primary narrative focus or central subject of a given work.
-
B.
narrativeSettingOfWork
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
-
C.
narrativeThemeInvolvement
Indicates that an entity participates in or contributes to a particular narrative theme within a story or discourse.
-
D.
coreNarrative
Indicates the primary storyline or central sequence of events that forms the main thread of a narrative.
-
E.
narrativeConcept
Indicates a conceptual or thematic element within a narrative, such as an idea, motif, or organizing principle that shapes the story’s structure or meaning.
- F. None of above. chosen
Provenance (4 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f6200ac60481909895c61d050b1338 |
completed | May 2, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61f109ef48190873bfe18638d2046 |
completed | May 2, 2026, 3:58 p.m. |
Created at: April 21, 2026, 1:03 p.m.