Triple
T33793755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freiburg |
E866007
|
entity |
| Predicate | historicCenterType |
P198321
|
FINISHED |
| Object | medieval old town |
—
|
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: medieval old town | Statement: [Freiburg, historicCenterType, medieval old town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicCenterType Context triple: [Freiburg, historicCenterType, medieval old town]
-
A.
hasHistoricCenterCharacteristic
chosen
Indicates that an entity possesses a specific attribute or quality related to the characteristics of a historic center.
-
B.
historicalCenterFor
Indicates that one entity has served as a central or focal place of historical significance, activity, or development for another entity.
-
C.
hasHistoricCenterStatus
Indicates that an entity has been designated or recognized as a historic center, typically due to its cultural, architectural, or historical significance.
-
D.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
E.
hasHistoricCenterShape
Indicates the geometric form or configuration that characterizes the historic center of a place or settlement.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: May 1, 2026, 1:46 a.m.