Triple
T18592411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Höchstadt an der Aisch |
E454401
|
entity |
| Predicate | hasHistoricTownFortifications |
P29117
|
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: [Höchstadt an der Aisch, hasHistoricTownFortifications, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricTownFortifications Context triple: [Höchstadt an der Aisch, hasHistoricTownFortifications, true]
-
A.
containsHistoricFort
Indicates that a place or area includes within its boundaries a historic fort.
-
B.
hasHistoricTownWallsRemnants
chosen
Indicates that remnants of historic town walls are present and associated with the subject entity.
-
C.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
D.
hasCastleTownHistory
Indicates that an entity has a historical association with a castle town, such as originating from, being located in, or significantly shaped by one.
-
E.
separatesHistoricTownsOf
Indicates that one entity serves as a dividing line or barrier between two or more historic towns.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b6792481908eae92718aa4c889 |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.