Triple
T38527100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady in the Dark universe |
E923256
|
entity |
| Predicate | originatesFromWorkPremieredIn |
P143079
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Lady in the Dark universe, originatesFromWorkPremieredIn, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromWorkPremieredIn Context triple: [Lady in the Dark universe, originatesFromWorkPremieredIn, 1941]
-
A.
createdForWorkPremieredIn
Indicates that a work was created specifically for a particular premiere event that took place in a given location or context.
-
B.
premieredInWorkPremiereYear
chosen
Indicates the year in which a work (such as a performance, film, or composition) had its first public premiere.
-
C.
partOfPremiereWork
Indicates that something is a component or segment belonging to a larger premiere work or initial presentation.
-
D.
placeOfWorkPremiere
Indicates the location where a person’s work or performance was first publicly presented or debuted.
-
E.
premieredWorkBy
Indicates that a creative work had its first public performance, showing, or presentation conducted by the specified entity.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.