Triple
T32293086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortified Region of Metz |
E825018
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | fortified region |
C17842
|
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: fortified region Context triple: [Fortified Region of Metz, instanceOf, fortified region]
-
A.
fortified town
A fortified town is a settlement enclosed by defensive structures such as walls, towers, and gates, designed to protect its inhabitants and resources from external threats.
-
B.
fortified settlement
A fortified settlement is a community enclosed by defensive structures such as walls, ramparts, or palisades, designed to protect its inhabitants and resources from external threats.
-
C.
fortified enclosure
chosen
A fortified enclosure is a defended area surrounded by protective barriers such as walls, ramparts, or palisades, designed to control access and provide security against external threats.
-
D.
fortified pass
A fortified pass is a strategically important narrow route through difficult terrain that has been strengthened with defensive structures to control movement and resist enemy forces.
-
E.
fortified battlefield sector
A fortified battlefield sector is a defined area of the front line that has been heavily strengthened with defensive structures, obstacles, and support assets to resist enemy attack and control key terrain.
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:44 a.m.