Triple
T31330364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Doll’s House, Part 2 |
E799006
|
entity |
| Predicate | settingTimeAfterEventsOf |
P136829
|
FINISHED |
| Object | A Doll’s House |
—
|
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: A Doll’s House | Statement: [A Doll’s House, Part 2, settingTimeAfterEventsOf, A Doll’s House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingTimeAfterEventsOf Context triple: [A Doll’s House, Part 2, settingTimeAfterEventsOf, A Doll’s House]
-
A.
settingAfterEvent
Indicates that a particular setting or state occurs subsequent to, and as a result of or in temporal sequence with, a specified event.
-
B.
setAfterEventsOf
chosen
Indicates that one event or state is positioned or scheduled to occur after the completion of one or more specified preceding events.
-
C.
settingAfter
Indicates that one setting or configuration occurs or is applied after another in a sequence or order.
-
D.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
E.
timePeriodAfter
Indicates that one time period occurs entirely later than another time period in a temporal sequence.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 9:16 p.m.