Triple
T28141571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old town fortifications of Landsberg am Lech |
E714354
|
entity |
| Predicate | hasSignificantModificationDate |
P25399
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [Old town fortifications of Landsberg am Lech, hasSignificantModificationDate, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignificantModificationDate Context triple: [Old town fortifications of Landsberg am Lech, hasSignificantModificationDate, 14th century]
-
A.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
B.
laterModifiedInPeriod
Indicates that one entity was modified at a later time than another entity within the same defined time period.
-
C.
modifiedAs
Indicates that one entity has been altered, changed, or revised into another form, version, or state.
-
D.
isModifiedAs
Indicates that an entity has been altered or changed from its original state in some specified manner.
-
E.
modificationDate
chosen
Indicates the date and time at which an entity was last changed or updated.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 9:53 p.m.