Triple
T36366109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hôtel de ville de Montbéliard |
E895628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | monument historique potentiel |
C1885
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: monument historique potentiel Context triple: [Hôtel de ville de Montbéliard, instanceOf, monument historique potentiel]
-
A.
cultural heritage monument
A cultural heritage monument is a historically, artistically, or culturally significant structure or site that embodies the identity, memory, and values of a community or civilization and is preserved for present and future generations.
-
B.
historic monument
chosen
A historic monument is a significant structure, site, or object preserved for its cultural, architectural, or historical importance, symbolizing and commemorating events, people, or eras of the past.
-
C.
revitalised historic site
A revitalised historic site is a formerly deteriorated or underused heritage location that has been carefully restored and adapted for contemporary use while preserving its cultural and historical significance.
-
D.
historicBuilding
A historicBuilding is a structure of significant age recognized for its cultural, architectural, or historical importance and often preserved or protected for future generations.
-
E.
medieval architecture monument
A medieval architecture monument is a historically significant structure from the Middle Ages that exemplifies characteristic building styles, materials, and decorative elements of its period and culture.
- F. None of above.
Provenance (1 batch)
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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.