Triple
T37321577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jassie Vandy |
E926492
|
entity |
| Predicate | primaryConcernInPlot |
P20493
|
FINISHED |
| Object | safety of her children |
—
|
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: safety of her children | Statement: [Jassie Vandy, primaryConcernInPlot, safety of her children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryConcernInPlot Context triple: [Jassie Vandy, primaryConcernInPlot, safety of her children]
-
A.
primaryIssue
Indicates that the related item is the main or most important issue among a set of issues.
-
B.
narrativeConcern
chosen
Indicates a relationship where something is thematically or structurally focused on, revolves around, or is primarily about a particular narrative topic or issue.
-
C.
primaryStoryThemes
Indicates the main recurring ideas or motifs that characterize and unify a story’s narrative.
-
D.
problemInPlot
Indicates that there is an issue, flaw, or inconsistency present within the structure or progression of a plot.
-
E.
primaryFunctionInPlot
Indicates the main narrative role or purpose that an entity serves within the plot of a story.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.