Triple
T9194516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verfall einer Familie |
E220669
|
entity |
| Predicate | relatedWorkOriginalLanguage |
P34465
|
FINISHED |
| Object | German |
—
|
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: German | Statement: [Verfall einer Familie, relatedWorkOriginalLanguage, German]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedWorkOriginalLanguage Context triple: [Verfall einer Familie, relatedWorkOriginalLanguage, German]
-
A.
originalLanguageOfWholeWork
Indicates that a given language is the primary or original language in which an entire work (such as a book, film, or other complete creation) was first produced or expressed.
-
B.
originalWorkFrom
Indicates that something is derived, adapted, or based on an earlier original work created by another source.
-
C.
languageOfParentWork
chosen
Indicates that the specified language is the language in which the parent (original or containing) work is expressed.
-
D.
originalLanguageAuthor
Indicates that an author created a work in a particular original language.
-
E.
collectionOriginalLanguage
Indicates the language in which a collection was originally created or first expressed.
- 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_69ca83e7ba70819088b74866d9da2c30 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd5c3614c81909e26417e00fdfa11 |
completed | April 1, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69cc660af2408190ae06eb8326e1c64e |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:25 p.m.