Triple
T22687258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newhaven |
E560948
|
entity |
| Predicate | hasMarinaOrHarbour |
P3007
|
FINISHED |
| Object | Newhaven Yacht Squadron marina |
—
|
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: Newhaven Yacht Squadron marina | Statement: [Newhaven, hasMarinaOrHarbour, Newhaven Yacht Squadron marina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarinaOrHarbour Context triple: [Newhaven, hasMarinaOrHarbour, Newhaven Yacht Squadron marina]
-
A.
hasHarbourEntrance
Indicates that an entity serves as the entrance or access point to a harbour for another entity.
-
B.
hasMainHarbourOnIsland
Indicates that the primary harbour of a place or region is located on a specific island.
-
C.
hasHarbor
chosen
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
D.
harbours
Indicates that one entity provides shelter, refuge, or concealment for another, often by keeping it safe or hidden.
-
E.
hasMarinaStatus
Indicates that an entity has a specific status or classification related to a marina (e.g., operational, planned, closed).
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178649aac8190a9d41f5d82895bdf |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.