Triple
T28001426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ereignis |
E707157
|
entity |
| Predicate | difficultToTranslate |
P163611
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ereignis, difficultToTranslate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: difficultToTranslate Context triple: [Ereignis, difficultToTranslate, true]
-
A.
isDifficultInLanguage
Indicates that performing or understanding an action, concept, or task is considered difficult when expressed or handled in a particular language.
-
B.
difficultToAnalyzeAs
Indicates that one entity is hard to examine, interpret, or understand when considered in terms of, or compared to, another entity.
-
C.
translatedIn
Indicates that a work, text, or content has been rendered from its original language into another specified language or linguistic form.
-
D.
possiblyTranslatedFrom
Indicates that one item may be a translation of another, but this relationship is uncertain or not definitively established.
-
E.
widelyTranslated
Indicates that a work has been translated into many different languages or versions, reflecting broad international dissemination.
- 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_69f63bd17884819090b08f0819bebe78 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 7:57 p.m.