Triple
T12943216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nurse (A Streetcar Named Desire) |
E309688
|
entity |
| Predicate | workContextTimePeriod |
P32393
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [The Nurse (A Streetcar Named Desire), workContextTimePeriod, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workContextTimePeriod Context triple: [The Nurse (A Streetcar Named Desire), workContextTimePeriod, mid-20th century]
-
A.
workPeriod
Indicates the span of time during which an entity is engaged in a particular work or employment activity.
-
B.
partOfWorkPeriod
Indicates that a specific time span is contained within, and belongs to, a larger defined work period.
-
C.
workSettingPeriod
chosen
Indicates the time period during which a particular work setting or employment context is in effect.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timePeriodCategory
Indicates the classification of a time period into a specific category or type (e.g., era, phase, or temporal grouping).
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.