Triple
T8191542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neustadt an der Aisch |
E191320
|
entity |
| Predicate | hasHistoricTownWalls |
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: [Neustadt an der Aisch, hasHistoricTownWalls, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricTownWalls Context triple: [Neustadt an der Aisch, hasHistoricTownWalls, true]
-
A.
hasHistoricTownWallsRemnants
chosen
Indicates that remnants of historic town walls are present and associated with the subject entity.
-
B.
hasCityWallName
Indicates that a city wall is associated with a specific name or designation.
-
C.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
-
D.
hasHistoricCenterStatus
Indicates that an entity has been designated or recognized as a historic center, typically due to its cultural, architectural, or historical significance.
-
E.
hasHistoricCity
Indicates that an entity possesses, contains, or is associated with a city recognized for its historical significance.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4da4a6f08190be8088a28d928341 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.