Triple
T36292144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Wucht XXII |
E893257
|
entity |
| Predicate | subjectMatterCharacteristic |
P99469
|
FINISHED |
| Object | open-ended symbolism |
—
|
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: open-ended symbolism | Statement: [Die Wucht XXII, subjectMatterCharacteristic, open-ended symbolism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectMatterCharacteristic Context triple: [Die Wucht XXII, subjectMatterCharacteristic, open-ended symbolism]
-
A.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
B.
subjectMatterScope
Indicates the thematic or topical domain that an action, statement, or resource pertains to or falls within.
-
C.
entityCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
-
D.
valueCharacteristic
Indicates that one entity serves as a value or specific quantitative/qualitative measure that characterizes or describes another entity.
-
E.
subjectHasCharacteristic
chosen
Indicates that a subject possesses, exhibits, or is defined by a particular characteristic or attribute.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:09 p.m.