Triple
T24237829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Palling |
E603137
|
entity |
| Predicate | hasSeaDefenceType |
P45947
|
FINISHED |
| Object | offshore breakwaters |
—
|
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: offshore breakwaters | Statement: [Sea Palling, hasSeaDefenceType, offshore breakwaters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaDefenceType Context triple: [Sea Palling, hasSeaDefenceType, offshore breakwaters]
-
A.
shipDefenseType
Indicates the specific kind of defensive system or protection mechanism that a ship employs.
-
B.
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).
-
C.
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.
-
D.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
E.
isFortifiedWith
Indicates that one entity has been strengthened, enriched, or supplemented by the addition of another entity.
- 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28a9c5c3081909cfddc8d29121817 |
completed | April 29, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.