Triple
T30282705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramsgate |
E770143
|
entity |
| Predicate | hasHarbourStatus |
P33212
|
FINISHED |
| Object | Royal Harbour |
—
|
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: Royal Harbour | Statement: [Ramsgate, hasHarbourStatus, Royal Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHarbourStatus Context triple: [Ramsgate, hasHarbourStatus, Royal Harbour]
-
A.
hasHarbor
Indicates that a place possesses or contains a harbor for docking or sheltering vessels.
-
B.
hasHarbourAuthority
Indicates that one entity holds official authority or administrative control over the operations and management of a harbour associated with another entity.
-
C.
hasSeaportStatus
chosen
Indicates that an entity possesses the status or designation of being a seaport or having seaport facilities.
-
D.
hasHarbormaster
Indicates that an entity has, is assigned, or is overseen by a specific harbormaster responsible for managing its harbor-related operations.
-
E.
hasHarborOpened
Indicates that a harbor has been officially opened and is available for use or operation.
- 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 7:45 p.m.