Triple
T7040992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Montbéliard |
E163509
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historic principality |
C5588
|
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: historic principality Context triple: [County of Montbéliard, instanceOf, historic principality]
-
A.
hereditary principality
A hereditary principality is a sovereign or semi-sovereign territory ruled by a prince whose authority and title are passed down through a family line, typically by primogeniture or other dynastic succession rules.
-
B.
historic city-state
A historic city-state is an independent, self-governing urban center and its surrounding territory that functioned as a sovereign political, economic, and cultural entity in a specific historical period.
-
C.
historic state
chosen
A historic state is a former political entity or government that once exercised sovereignty over a defined territory and population but has since ceased to exist in its original form.
-
D.
historic palace
A historic palace is a grand, architecturally significant residence once occupied by royalty or nobility, preserved as a cultural landmark that reflects the political, social, and artistic heritage of its era.
-
E.
historic region
A historic region is a geographically defined area recognized for its significant past events, cultural heritage, or historical identity that has shaped its development over time.
- 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_69c6885e7c1c8190be32a8f79ab4e0cf |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:36 p.m.