Triple
T26758196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exilliteratur |
E674724
|
entity |
| Predicate | hatBedeutendeGattungen |
P162817
|
FINISHED |
| Object | Tagebuch |
—
|
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: Tagebuch | Statement: [Exilliteratur, hatBedeutendeGattungen, Tagebuch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatBedeutendeGattungen Context triple: [Exilliteratur, hatBedeutendeGattungen, Tagebuch]
-
A.
hatBedeutendeGattungen
chosen
Indicates that an entity has or is associated with significant or important categories or types.
-
B.
notableGenus
Indicates that one entity is a genus that is especially prominent, well-known, or significant in relation to the other entity.
-
C.
recognizedGenera
Indicates that one entity formally acknowledges or accepts another entity as a valid genus within a taxonomic or classificatory system.
-
D.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
E.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
- 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_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:56 a.m.