Triple
T4358518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seaton Carew |
E98608
|
entity |
| Predicate | hasCoastalOrientation |
P45094
|
FINISHED |
| Object | east-facing coast |
—
|
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: east-facing coast | Statement: [Seaton Carew, hasCoastalOrientation, east-facing coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalOrientation Context triple: [Seaton Carew, hasCoastalOrientation, east-facing coast]
-
A.
coastOrientation
chosen
Indicates the directional alignment or facing direction of a coastline relative to the cardinal or geographic axes.
-
B.
hasCoastalPath
Indicates that there exists a designated path or route running along or adjacent to the coastline of a given area or feature.
-
C.
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.
-
D.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
E.
hasCoastlineType
Indicates the specific nature or classification of the coastline associated with a geographic entity.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c7fa1881908bdc844a7142eb65 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.