Triple
T27603462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Corinthian Yacht Club |
E700114
|
entity |
| Predicate | clubhouseHasFeature |
P164510
|
FINISHED |
| Object | riverside terraces |
—
|
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: riverside terraces | Statement: [Royal Corinthian Yacht Club, clubhouseHasFeature, riverside terraces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubhouseHasFeature Context triple: [Royal Corinthian Yacht Club, clubhouseHasFeature, riverside terraces]
-
A.
clubhouseStyle
Indicates that one entity has a clubhouse characterized by a particular architectural or design style specified by the other entity.
-
B.
hasClubhouseAccess
Indicates that an entity is permitted to enter or use the facilities, services, or privileges of a clubhouse.
-
C.
clubhouseCompletedIn
Indicates that the construction or development of a clubhouse was finished in a specified time or year.
-
D.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
E.
hasClubhouses
Indicates that an entity possesses, manages, or is associated with one or more clubhouses.
- 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f64e6e8c9081908ce4d364aa26147a |
completed | May 2, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 27, 2026, 2:09 p.m.