Triple
T38465371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dr. Lilith Sternin |
E912548
|
entity |
| Predicate | settingOfPrimaryStories |
P195301
|
FINISHED |
| Object | Boston |
—
|
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: Boston | Statement: [Dr. Lilith Sternin, settingOfPrimaryStories, Boston]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfPrimaryStories Context triple: [Dr. Lilith Sternin, settingOfPrimaryStories, Boston]
-
A.
settingOfManyStories
Indicates that the subject serves as the location or environment where many different stories take place.
-
B.
primaryStoryThemes
Indicates the main recurring ideas or motifs that characterize and unify a story’s narrative.
-
C.
timePeriodOfPrimaryStories
Indicates the time period during which the primary stories or main narrative events of something (e.g., a work or series) take place.
-
D.
mainSettingOfStory
Indicates that a location or environment serves as the primary setting in which the events of a story take place.
-
E.
primarySettingOf
Indicates that a location or context serves as the main or principal setting in which an entity (such as a story, event, or activity) takes place.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
| PDg | Predicate description generation | batch_69fdb4544b548190b8971f8055d48caa |
completed | May 8, 2026, 10 a.m. |
Created at: May 3, 2026, 4:31 p.m.