Triple
T8337669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hattingen |
E195827
|
entity |
| Predicate | hasOldTownStatus |
P53191
|
FINISHED |
| Object | protected historic center |
—
|
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: protected historic center | Statement: [Hattingen, hasOldTownStatus, protected historic center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldTownStatus Context triple: [Hattingen, hasOldTownStatus, protected historic center]
-
A.
oldTownStatus
chosen
Indicates that a place holds the designation or characteristics of being an old or historic town.
-
B.
hasNewTownStatus
Indicates that an entity has been granted or holds the official status of a newly established town.
-
C.
hasTownStatus
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
-
D.
hasMarketTownStatus
Indicates that a settlement holds the official legal or historical status of being recognized as a market town.
-
E.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd5027c81909724f25aa30bbe58 |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:57 p.m.