Triple
T6929574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strehlen, Prussian Silesia |
E160397
|
entity |
| Predicate | timePeriodAsPrussianTown |
P47006
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Strehlen, Prussian Silesia, timePeriodAsPrussianTown, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodAsPrussianTown Context triple: [Strehlen, Prussian Silesia, timePeriodAsPrussianTown, 19th century]
-
A.
timeInKingdomOfPrussia
chosen
Indicates that an entity spent a specified period of time within the Kingdom of Prussia.
-
B.
startOfKingshipInPrussia
Indicates the point in time when an entity begins its reign or kingship in Prussia.
-
C.
timePeriodAsDanishTerritory
Indicates that, during a specified time period, the referenced place or region was under Danish territorial control or sovereignty.
-
D.
PrussianStrengthApprox
Indicates an approximate assessment or estimation of the strength or power associated with Prussia in a given context.
-
E.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
- 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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6da1f5fcc8190b43f53f90fc1821c |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bb577c81908ee8b415b4281f3d |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:27 p.m.