Triple
T21081466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnllundain |
E519378
|
entity |
| Predicate | isCoastalFeature |
P75701
|
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: [Carnllundain, isCoastalFeature, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCoastalFeature Context triple: [Carnllundain, isCoastalFeature, true]
-
A.
containsCoastalFeature
Indicates that one entity geographically includes or encompasses a coastal feature (such as a beach, cliff, bay, or shoreline) within its area or boundaries.
-
B.
hasCoastalCharacteristic
chosen
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
-
C.
isCoastalArea
Indicates that a given area is located along or directly adjacent to a sea or ocean coastline.
-
D.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
-
E.
isCoastalRegion
Indicates that a region is located along or directly adjacent to a sea or ocean 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702db430c81908a1547d8fbe45506 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:49 p.m.