Triple
T36256102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristelmestune |
E891940
|
entity |
| Predicate | isCoastalSettlementName |
P184819
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bristelmestune, isCoastalSettlementName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalSettlementName Context triple: [Bristelmestune, isCoastalSettlementName, true]
-
A.
coastalSettlementOf
Indicates a relationship where a settlement is located on or near the coast of a specified geographic area or body of water.
-
B.
isCoastalSettlementOf
Indicates that a settlement is located on or near the coast within the territory of a specified geographic or administrative area.
-
C.
isCoastalSettlementPortFor
Indicates that a coastal settlement functions as a port serving a particular area, route, or entity for maritime access and activities.
-
D.
isCoastalCityLocality
Indicates that a city or locality is situated on or very near a sea or ocean coastline.
-
E.
isCoastalCommunityName
Indicates that the named place is recognized as a community located on or very near a coastline.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5fdfd088190a4f1290b9b7cd387 |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b57aa0848190a22c31c3ff90e0ab |
completed | May 3, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:09 p.m.