Triple
T16711168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holderness |
E406108
|
entity |
| Predicate | hasSeaDefenceStructure |
P45947
|
FINISHED |
| Object | groynes at Mappleton |
—
|
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: groynes at Mappleton | Statement: [Holderness, hasSeaDefenceStructure, groynes at Mappleton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeaDefenceStructure Context triple: [Holderness, hasSeaDefenceStructure, groynes at Mappleton]
-
A.
hasFortifications
Indicates that one entity possesses or is equipped with defensive structures or fortification works associated with it.
-
B.
shareDefenseStructure
Indicates that two or more entities utilize or are protected by the same defensive structure or system.
-
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.
isFortificationGatewayOf
Indicates that a gateway or entrance structure serves as an access point or defensive portal belonging to a specific fortification.
-
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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e386523fc08190a13a4232af191992 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.