Triple
T28001831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Das Unbehagen in der Kultur |
E707166
|
entity |
| Predicate | standardEditionVolume |
P169951
|
FINISHED |
| Object | 21 |
—
|
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: 21 | Statement: [Das Unbehagen in der Kultur, standardEditionVolume, 21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardEditionVolume Context triple: [Das Unbehagen in der Kultur, standardEditionVolume, 21]
-
A.
standardEditionPublisher
Indicates that an entity serves as the publisher responsible for issuing the standard edition of another work or resource.
-
B.
standardEditionTracks
Indicates that the related tracks are those included in the standard (non-deluxe) edition of a release.
-
C.
isStandardEditionOf
Indicates that one entity is the regular, non-special version of another entity, typically lacking extra features, content, or enhancements found in other editions.
-
D.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
E.
serverEdition
Indicates the specific edition or variant of a server within a broader server product or family.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 27, 2026, 7:57 p.m.