Triple
T22885514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rowes Wharf |
E567592
|
entity |
| Predicate | hasMarinaCapacity |
P128295
|
FINISHED |
| Object | approximately 30–40 slips |
—
|
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: approximately 30–40 slips | Statement: [Rowes Wharf, hasMarinaCapacity, approximately 30–40 slips]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarinaCapacity Context triple: [Rowes Wharf, hasMarinaCapacity, approximately 30–40 slips]
-
A.
marinaCapacity
chosen
Indicates the maximum number of boats or berths that a marina is designed or allowed to accommodate.
-
B.
hasMarinaStatus
Indicates that an entity has a specific status or classification related to a marina (e.g., operational, planned, closed).
-
C.
hasMarinaService
Indicates that an entity provides marina-related services or facilities for boats and watercraft.
-
D.
hasMarinaName
Indicates that an entity (such as a marina) is associated with a specific name identifying that marina.
-
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.
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_69e2458a92ec81908fc1cd5f6407d2ab |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17fc0cdb081908107d40069d9735f |
completed | April 29, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:40 p.m.