Triple
T22266627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yser estuary locks |
E550367
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Belgian coastal defense system |
—
|
NE NERFINISHED |
How this triple was built (3 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: Belgian coastal defense system | Statement: [Yser estuary locks, partOf, Belgian coastal defense system]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Belgian coastal defense system Context triple: [Yser estuary locks, partOf, Belgian coastal defense system]
-
A.
Dutch barrier fortress system
The Dutch barrier fortress system was a network of strategically located fortified towns and strongholds designed to protect the Dutch Republic’s southern frontier, particularly against French expansion in the 17th and 18th centuries.
-
B.
Fortress Hellevoetsluis
Fortress Hellevoetsluis is a historic coastal fortification in the Dutch town of Hellevoetsluis, known for its maritime defense role and well-preserved military architecture.
-
C.
Amsterdam city defense system
The Amsterdam city defense system was the historical network of fortifications, militias, and protective works that safeguarded the city of Amsterdam from external threats.
-
D.
Akkerman Fortress
Akkerman Fortress is a well-preserved medieval citadel in Bilhorod-Dnistrovskyi, Ukraine, known for its massive stone walls overlooking the Dniester estuary and its role in regional military history.
-
E.
Maginot Line
The Maginot Line was a vast system of French defensive fortifications built along the country’s eastern border before World War II, intended to deter a German invasion.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Belgian coastal defense system Target entity description: The Belgian coastal defense system is an integrated network of sea walls, dunes, floodgates, and hydraulic structures designed to protect Belgium’s North Sea coastline and low-lying inland areas from storm surges and flooding.
-
A.
Dutch barrier fortress system
The Dutch barrier fortress system was a network of strategically located fortified towns and strongholds designed to protect the Dutch Republic’s southern frontier, particularly against French expansion in the 17th and 18th centuries.
-
B.
Fortress Hellevoetsluis
Fortress Hellevoetsluis is a historic coastal fortification in the Dutch town of Hellevoetsluis, known for its maritime defense role and well-preserved military architecture.
-
C.
Amsterdam city defense system
The Amsterdam city defense system was the historical network of fortifications, militias, and protective works that safeguarded the city of Amsterdam from external threats.
-
D.
Akkerman Fortress
Akkerman Fortress is a well-preserved medieval citadel in Bilhorod-Dnistrovskyi, Ukraine, known for its massive stone walls overlooking the Dniester estuary and its role in regional military history.
-
E.
Maginot Line
The Maginot Line was a vast system of French defensive fortifications built along the country’s eastern border before World War II, intended to deter a German invasion.
- F. None of above. chosen
Provenance (2 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_69e11e43d8208190aff4f9cf7f2c2a8a |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f141bc458c81909837373d749b915d |
completed | April 28, 2026, 11:24 p.m. |
Created at: April 16, 2026, 8:39 p.m.