Triple
T2375281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dennis Village |
E46182
|
entity |
| Predicate | coastalSettlementType |
P14278
|
FINISHED |
| Object | seaside village |
—
|
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: seaside village | Statement: [Dennis Village, coastalSettlementType, seaside village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalSettlementType Context triple: [Dennis Village, coastalSettlementType, seaside village]
-
A.
humanSettlementType
chosen
Indicates the classification of a human settlement based on its form or function, such as village, town, or city.
-
B.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
-
C.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
D.
basedOnCoast
Indicates that something is situated along, adjacent to, or directly influenced by a coastline.
-
E.
traditionalSettlement
Indicates that an entity is a settlement characterized by long-established, customary, or historically rooted patterns of habitation and land use.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.