Triple
T28889338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Rose Dawson Calvert |
E732652
|
entity |
| Predicate | flashbackStructure |
P165486
|
FINISHED |
| Object | her memories form the main plot |
—
|
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: her memories form the main plot | Statement: [Old Rose Dawson Calvert, flashbackStructure, her memories form the main plot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flashbackStructure Context triple: [Old Rose Dawson Calvert, flashbackStructure, her memories form the main plot]
-
A.
portrayedInFlashbacks
Indicates that an entity appears or is depicted specifically within flashback scenes of a narrative work.
-
B.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
C.
flashType
Indicates the type or mode of flash used or associated with an event, object, or action.
-
D.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
-
E.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a744e1c8190bff56db4cb0b68df |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 7:53 a.m.