Triple
T19514714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innere Stadt |
E488246
|
entity |
| Predicate | wasFortifiedUntil |
P77894
|
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: [Innere Stadt, wasFortifiedUntil, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFortifiedUntil Context triple: [Innere Stadt, wasFortifiedUntil, 19th century]
-
A.
wasFortifiedBy
Indicates that a place or structure received defensive strengthening or fortification through the actions or resources of a specified agent or entity.
-
B.
eraOfFortification
chosen
Indicates the historical time period during which a structure or site was fortified or equipped with defensive works.
-
C.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
-
D.
dateOfFortification
Indicates the specific date or time period when a structure or site was fortified or had defensive works constructed or significantly strengthened.
-
E.
eraOfMajorFortification
Indicates the historical period during which a structure or site underwent its primary or most significant phase of fortification.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359a7070819099d925447c80bf23 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.