Triple
T30398493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunningdale Golf Club |
E773284
|
entity |
| Predicate | OldCourseStyle |
P60439
|
FINISHED |
| Object | heathland |
—
|
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: heathland | Statement: [Sunningdale Golf Club, OldCourseStyle, heathland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OldCourseStyle Context triple: [Sunningdale Golf Club, OldCourseStyle, heathland]
-
A.
heritageStyle
Indicates that one entity is characterized by, designed in, or associated with a particular heritage or traditional style defined by the other entity.
-
B.
agedStyle
Indicates a relationship where something has a particular age-related style, appearance, or aesthetic (e.g., old-fashioned, vintage, or time-worn).
-
C.
traditionalStyle
chosen
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
D.
moreTraditionalThan
Indicates that one entity adheres more strongly to traditional customs, values, or practices than another entity.
-
E.
styleReminiscentOf
Indicates that one entity’s style closely recalls, echoes, or is strongly influenced by the style of 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686150f908190ba57742775f07870 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:03 p.m.