Triple
T26758186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exilliteratur |
E674724
|
entity |
| Predicate | istAbzugrenzenVon |
P161201
|
FINISHED |
| Object | NS-konforme Literatur |
—
|
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: NS-konforme Literatur | Statement: [Exilliteratur, istAbzugrenzenVon, NS-konforme Literatur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: istAbzugrenzenVon Context triple: [Exilliteratur, istAbzugrenzenVon, NS-konforme Literatur]
-
A.
istAbzugrenzenVon
chosen
Indicates that one entity must be distinguished or differentiated from another entity.
-
B.
separatesTerritoryOf
Indicates that one entity serves as a boundary or divider between the territories or domains of two other entities.
-
C.
borderDialectOf
Indicates a dialect that is spoken in a border area and is linguistically associated with or derived from a particular neighboring language or dialect.
-
D.
borderingAuthorityOf
Indicates that one authority’s jurisdiction directly touches or shares a boundary with another authority’s jurisdiction.
-
E.
wasExclaveOf
Indicates that a territory or region was geographically separated from its main governing state and politically belonged to that state as an exclave.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618d6dad48190b2bcb3ddf080dadf |
completed | May 2, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 3:56 a.m.