Triple
T28212307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke (The Notebook character) |
E711205
|
entity |
| Predicate | storyTimePeriodDescribed |
P11197
|
FINISHED |
| Object | 1940s |
—
|
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: 1940s | Statement: [Duke (The Notebook character), storyTimePeriodDescribed, 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyTimePeriodDescribed Context triple: [Duke (The Notebook character), storyTimePeriodDescribed, 1940s]
-
A.
storyTime
Indicates that one entity is narrating or sharing a story with another entity, typically in a designated or scheduled period for storytelling.
-
B.
timeOfNarrative
chosen
Indicates the specific time or period during which the events of a narrative are set or unfold.
-
C.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
D.
originStoryIncludes
Indicates that an entity’s origin story contains, involves, or features the referenced element as a component or part of that backstory.
-
E.
retellsStoryOf
Indicates that one entity recounts or narrates the story originally told or experienced by 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 10:40 p.m.