Triple
T10832433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal and Ancient Golf Club of St Andrews clubhouse |
E255656
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | golf-related building |
C10042
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: golf-related building Context triple: [Royal and Ancient Golf Club of St Andrews clubhouse, instanceOf, golf-related building]
-
A.
golf landmark
chosen
A golf landmark is a notable or distinctive feature on or near a golf course—such as a famous hole, tree, bunker, building, or natural formation—that serves as a point of reference, historical significance, or visual identity for players and spectators.
-
B.
golf course complex
A golf course complex is a large recreational facility that includes one or more golf courses along with supporting amenities such as a clubhouse, practice areas, pro shop, and often dining or lodging services.
-
C.
public golf course
A public golf course is a recreational facility with a series of golf holes, open to the general public for play, typically for a daily fee without requiring membership.
-
D.
private golf course
A private golf course is an exclusive, member-only golfing facility that offers controlled access to its grounds, amenities, and services, typically requiring membership fees or invitations.
-
E.
golf course chain
A golf course chain is a business entity that owns, operates, or franchises multiple golf courses under a unified brand, management structure, and service standards.
- F. None of above.
Provenance (1 batch)
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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:19 p.m.