Triple
T27603468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Corinthian Yacht Club |
E700114
|
entity |
| Predicate | hasSailingWaters |
P106673
|
FINISHED |
| Object | tidal estuary |
—
|
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: tidal estuary | Statement: [Royal Corinthian Yacht Club, hasSailingWaters, tidal estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSailingWaters Context triple: [Royal Corinthian Yacht Club, hasSailingWaters, tidal estuary]
-
A.
hasWaterFeatures
Indicates that an entity includes or is associated with water-related elements such as fountains, ponds, streams, or similar features.
-
B.
hasWatersOf
chosen
Indicates that a geographic or physical entity contains, is traversed by, or is otherwise characterized by specific bodies or types of water.
-
C.
hasSurroundingWaters
Indicates that one entity is bordered or encircled by bodies of water associated with another entity.
-
D.
usesWaterwaysFor
Indicates that one entity relies on or employs waterways as a means or route to perform an activity or function in relation to another entity.
-
E.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2:09 p.m.