Triple
T30017322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Das himmlische Leben |
E762629
|
entity |
| Predicate | usesVoice |
P55263
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Das himmlische Leben, usesVoice, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVoice Context triple: [Das himmlische Leben, usesVoice, yes]
-
A.
usesVoiceAssistant
Indicates that an entity regularly operates or interacts with a voice-controlled digital assistant.
-
B.
usesSampleOfSpeechBy
Indicates that one entity employs or incorporates a sample of speech produced by another entity.
-
C.
hasVoiceIn
chosen
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
D.
hasVoiceSystem
Indicates that one entity possesses or is equipped with a particular voice-based system or voice technology.
-
E.
hasVoicing
Indicates that one sound, segment, or phoneme is characterized by the presence or absence of vocal fold vibration (voicing) in relation to another or to a specified voicing property.
- 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_69f2246b0c84819094f1250b6a02d277 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6798536288190bd0541e060dd9f6a |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:46 p.m.