Triple
T28003628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glendun |
E707211
|
entity |
| Predicate | hasNearbyCoastalSettlement |
P193650
|
FINISHED |
| Object | Cushendun |
—
|
NE NERFINISHED |
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: Cushendun | Statement: [Glendun, hasNearbyCoastalSettlement, Cushendun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCoastalSettlement Context triple: [Glendun, hasNearbyCoastalSettlement, Cushendun]
-
A.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
B.
hasCoastlineSettlement
Indicates that a settlement is located on or directly adjacent to a coastline.
-
C.
isCoastalSettlementPortFor
Indicates that a coastal settlement functions as a port serving a particular area, route, or entity for maritime access and activities.
-
D.
isCoastalSettlementOf
Indicates that a settlement is located on or near the coast within the territory of a specified geographic or administrative area.
-
E.
coastalSettlementOf
Indicates a relationship where a settlement is located on or near the coast of a specified geographic area or body of water.
- F. None of above. chosen
Provenance (4 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: April 27, 2026, 7:58 p.m.