Triple
T38322996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Von der großen Sehnsucht |
E1036705
|
entity |
| Predicate | textualMode |
P5468
|
FINISHED |
| Object | meditative reflection |
—
|
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: meditative reflection | Statement: [Von der großen Sehnsucht, textualMode, meditative reflection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualMode Context triple: [Von der großen Sehnsucht, textualMode, meditative reflection]
-
A.
textMode
Indicates that something operates, is displayed, or is processed in a mode where information is handled primarily as text rather than as graphics or other media.
-
B.
textModes
Indicates a relationship where an entity supports or operates in specific textual modes or formats (such as plain text, rich text, or other text-based configurations).
-
C.
textualTransmission
Indicates the transfer or communication of information through written or printed text from one source to another.
-
D.
textualApproach
Indicates an approach or method that is based on or expressed through text or written language.
-
E.
textType
chosen
Indicates the classification of a text according to its type, format, or genre.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.