Triple
T36172598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Ocean Racing Club |
E1046185
|
entity |
| Predicate | hasClubhouseLocation |
P17431
|
FINISHED |
| Object | St James's, London |
—
|
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: St James's, London | Statement: [Royal Ocean Racing Club, hasClubhouseLocation, St James's, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClubhouseLocation Context triple: [Royal Ocean Racing Club, hasClubhouseLocation, St James's, London]
-
A.
hasClubhouseAccess
Indicates that an entity is permitted to enter or use the facilities, services, or privileges of a clubhouse.
-
B.
hasClubhouses
chosen
Indicates that an entity possesses, manages, or is associated with one or more clubhouses.
-
C.
isLocatedInCityWithClub
Indicates that an entity is situated in a city that has at least one (sports or similar) club based there.
-
D.
hasClub
Indicates that an entity is associated with or belongs to a particular club.
-
E.
hasHomeClub
Indicates that an entity (typically a person, such as an athlete) is associated with a particular club as their primary or official home organization.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: May 3, 2026, 4:08 p.m.