Triple
T16079810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theodor Fontane |
E390074
|
entity |
| Predicate | describedPrussianSociety |
P65295
|
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: [Theodor Fontane, describedPrussianSociety, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedPrussianSociety Context triple: [Theodor Fontane, describedPrussianSociety, true]
-
A.
commandStructurePrussia
Indicates the hierarchical command relationships within the Prussian military or administrative structure.
-
B.
suppressedInPrussia
Indicates that something (such as an activity, organization, or publication) was officially forbidden or repressed by the authorities in Prussia.
-
C.
timeInKingdomOfPrussia
Indicates that an entity spent a specified period of time within the Kingdom of Prussia.
-
D.
depictsSocietyType
chosen
Indicates that one entity visually represents or portrays the type or structure of a particular society associated with another entity.
-
E.
associatedRulerTitlePrussia
Indicates a relationship where a ruler’s title is specifically linked to or held in connection with Prussia.
- 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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1827ad7c88190b867da511cbfb7fa |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.