Triple
T23863037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Den Helder |
E592500
|
entity |
| Predicate | hasCoastalDefenceHistory |
P45947
|
FINISHED |
| Object | Napoleonic era fortifications |
—
|
LITERAL FINISHED |
How this triple was built (2 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: Napoleonic era fortifications | Statement: [Den Helder, hasCoastalDefenceHistory, Napoleonic era fortifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalDefenceHistory Context triple: [Den Helder, hasCoastalDefenceHistory, Napoleonic era fortifications]
-
A.
hasHistoricalRegionOnCoast
Indicates that a historical region is located along or adjacent to a coastline.
-
B.
coastalDefense
chosen
Indicates a defensive relationship in which structures, systems, or actions are used to protect a coastline or shore area from threats such as erosion, flooding, or attack.
-
C.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
D.
hasMaritimeHeritage
Indicates that an entity possesses a historical, cultural, or traditional connection to maritime activities, seafaring, or the sea.
-
E.
hasCoastlineSettlement
Indicates that a settlement is located on or directly adjacent to a coastline.
- F. None of above.
Provenance (3 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae16df4819081a8b3a395e45118 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.