Triple
T4511014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delfzijl |
E102053
|
entity |
| Predicate | hasSeaDefense |
P45947
|
FINISHED |
| Object | dikes |
—
|
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: dikes | Statement: [Delfzijl, hasSeaDefense, dikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaDefense Context triple: [Delfzijl, hasSeaDefense, dikes]
-
A.
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.
-
B.
hasNavalFacility
Indicates that one entity possesses, hosts, or contains a naval facility (such as a naval base, port, or installation) associated with it.
-
C.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
-
D.
hasSeaArmType
Indicates that an entity is associated with or characterized by a specific type of sea arm (such as a bay, gulf, fjord, or similar marine inlet).
-
E.
isNavalBase
Indicates that a location functions as a naval base, serving as an operational facility or station for naval forces.
- 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5712b9308190876c117b50d12635 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.