Triple
T25208604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Sydney Golf Club |
E631621
|
entity |
| Predicate | countryClubType |
P165300
|
FINISHED |
| Object | golf and sporting club |
—
|
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: golf and sporting club | Statement: [Royal Sydney Golf Club, countryClubType, golf and sporting club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryClubType Context triple: [Royal Sydney Golf Club, countryClubType, golf and sporting club]
-
A.
countryClubSetting
Indicates a setting or context that takes place within or is characteristic of a country club environment.
-
B.
homeCountryClub
Indicates that a country club is the primary or official club associated with a particular person or entity as their home club.
-
C.
countryClubAttitude
Indicates an attitude or mindset characterized by exclusivity, elitism, or social-club-style privilege in how someone relates to others or to a situation.
-
D.
hasCountryClubLocation
Indicates that a country club is located at, or associated with, a specific geographic place or address.
-
E.
hasGolfCourse
Indicates that one entity possesses, contains, or includes a golf course as part of its facilities or attributes.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f658a91ba0819084fbe3dd8a09f7cd |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f657f2c8b08190bfeb3173ef78207d |
completed | May 2, 2026, 8 p.m. |
Created at: April 21, 2026, 12:57 p.m.