Triple
T38648453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Masochism: Coldness and Cruelty and Venus in Furs |
E938778
|
entity |
| Predicate | featuresWorkOrigin |
P110586
|
FINISHED |
| Object | Austria |
E2895
|
NE 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: Austria | Statement: [Masochism: Coldness and Cruelty and Venus in Furs, featuresWorkOrigin, Austria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresWorkOrigin Context triple: [Masochism: Coldness and Cruelty and Venus in Furs, featuresWorkOrigin, Austria]
-
A.
workOriginatesFrom
Indicates that the creation, development, or initiation of a work can be traced back to a particular source, agent, or origin.
-
B.
describesOriginOf
Indicates that one entity specifies or explains the source, provenance, or origin of another entity.
-
C.
causeOfOrigin
Indicates that one entity is the source or initiating cause from which another entity originates or comes into existence.
-
D.
constructionOrigin
Indicates the source, cause, or initiating factor from which a construction or building project originates.
-
E.
placeOfOriginOfWork
chosen
Indicates the location where a work (such as an artwork, literary piece, or other creation) was originally produced or created.
- F. None of above.
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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41f430eb248190befef915b01ea498 |
completed | June 29, 2026, 4:27 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.