Triple
T13506105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dymchurch |
E321017
|
entity |
| Predicate | seaDefenceRole |
P37809
|
FINISHED |
| Object | protects Romney Marsh from flooding |
—
|
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: protects Romney Marsh from flooding | Statement: [Dymchurch, seaDefenceRole, protects Romney Marsh from flooding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaDefenceRole Context triple: [Dymchurch, seaDefenceRole, protects Romney Marsh from flooding]
-
A.
coastalDefense
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.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
C.
hasNavalRole
Indicates that an entity holds or is assigned a role, function, or duty within a naval or maritime context.
-
D.
coastRole
chosen
Indicates a role or function that an entity has specifically in relation to a coast or coastal area.
-
E.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf8259a08190ada13c4a3078f07d |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.