Triple
T33444658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The National Dream (TV miniseries) |
E856459
|
entity |
| Predicate | workLocationOfStory |
P45019
|
FINISHED |
| Object | Ottawa |
—
|
NE NERFINISHED |
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: Ottawa | Statement: [The National Dream (TV miniseries), workLocationOfStory, Ottawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workLocationOfStory Context triple: [The National Dream (TV miniseries), workLocationOfStory, Ottawa]
-
A.
locationOfNarrative
Indicates the place or setting where the events or story described in the narrative occur.
-
B.
homeLocationInStory
Indicates the place that serves as a character’s primary home or base of residence within the context of the story.
-
C.
narrativeSettingOfWork
chosen
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
-
D.
workLocationOfFictionalCharacter
Indicates the place or organization where a fictional character is depicted as working within their narrative context.
-
E.
worksOnStoryAbout
Indicates that one entity is actively engaged in creating, developing, or contributing to a story whose subject or focus is 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e4a7497c8190be81f04e99b769d4 |
completed | May 3, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:37 a.m.