Triple
T34483952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarborough North Bay beach |
E885264
|
entity |
| Predicate | hasCoastalDefences |
P45947
|
FINISHED |
| Object | groynes |
—
|
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 | Statement: [Scarborough North Bay beach, hasCoastalDefences, groynes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalDefences Context triple: [Scarborough North Bay beach, hasCoastalDefences, groynes]
-
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.
hasCoastalEnclave
Indicates that one territory possesses a non-contiguous portion of its land that is coastal and entirely surrounded by another territory.
-
C.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
D.
hasCoastline
Indicates that a geographic entity is bordered by and directly touches a sea or ocean along part of its boundary.
-
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_69f349c947fc81909d30b53c194d6ea1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:01 a.m.