Triple
T6507537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam city defense system |
E150048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical city defense system |
C876
|
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: historical city defense system Context triple: [Amsterdam city defense system, instanceOf, historical city defense system]
-
A.
military fortification system
chosen
A military fortification system is an integrated network of defensive structures, obstacles, and support facilities designed to protect territory, forces, and strategic assets from enemy attack.
-
B.
medieval city wall
A medieval city wall is a fortified defensive structure encircling a town or city, typically built of stone with towers, gates, and battlements to protect inhabitants from external threats.
-
C.
historic military fort
A historic military fort is a fortified structure or complex built in the past for defense and military operations, often preserved today as a cultural and historical landmark.
-
D.
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.
-
E.
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.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:43 p.m.