Triple
T24607267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neatishead |
E609007
|
entity |
| Predicate | hasMarinaOrStaithe |
P156721
|
FINISHED |
| Object | Neatishead Staithe |
—
|
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: Neatishead Staithe | Statement: [Neatishead, hasMarinaOrStaithe, Neatishead Staithe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarinaOrStaithe Context triple: [Neatishead, hasMarinaOrStaithe, Neatishead Staithe]
-
A.
hasMarinaStatus
Indicates that an entity has a specific status or classification related to a marina (e.g., operational, planned, closed).
-
B.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
C.
hasMarinaService
Indicates that an entity provides marina-related services or facilities for boats and watercraft.
-
D.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
-
E.
hasSeaAccess
Indicates that an entity has direct access to the sea, typically via a coastline, port, or navigable waterway connected to the sea.
- 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f2b8b8bc5881908df49c0b07110246 |
completed | April 30, 2026, 2:04 a.m. |
Created at: April 18, 2026, 2:31 a.m.