Triple
T3827795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Days of Our Lives |
E88732
|
entity |
| Predicate | mainSettingType |
P14490
|
FINISHED |
| Object | fictional Midwestern town |
—
|
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: fictional Midwestern town | Statement: [Days of Our Lives, mainSettingType, fictional Midwestern town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainSettingType Context triple: [Days of Our Lives, mainSettingType, fictional Midwestern town]
-
A.
primarySetting
Indicates that one entity serves as the main or central location, context, or environment in which the other entity’s events or activities primarily take place.
-
B.
primarySettingFeature
Indicates that a particular feature is the main or defining characteristic of a setting.
-
C.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
D.
primarySettingOf
chosen
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.
-
E.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
- 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_69aed9538cf881909d9ce8ca4ac7c18c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8459f881908a2c91bb07e381ef |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.