Triple
T14226482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Doll's Life |
E352629
|
entity |
| Predicate | settingAfter |
P113291
|
FINISHED |
| Object | events of A Doll's House |
—
|
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: events of A Doll's House | Statement: [A Doll's Life, settingAfter, events of A Doll's House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingAfter Context triple: [A Doll's Life, settingAfter, events of A Doll's House]
-
A.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
B.
secondarySetting
Indicates that an entity serves as an additional or supporting setting context for another entity, rather than being the primary setting.
-
C.
laterConfiguration
Indicates that one configuration occurs after another in time, representing a subsequent or later state relative to a prior configuration.
-
D.
settingControlled
Indicates that one entity regulates, adjusts, or determines the configuration or parameters of another entity.
-
E.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6228e53c8190abbe4e2d88a7362a |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:07 a.m.