Triple
T35271599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverrary golf community |
E1018682
|
entity |
| Predicate | countryClubAmenities |
P4286
|
FINISHED |
| Object | golf courses |
—
|
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 courses | Statement: [Inverrary golf community, countryClubAmenities, golf courses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryClubAmenities Context triple: [Inverrary golf community, countryClubAmenities, golf courses]
-
A.
countryClubSetting
Indicates a setting or context that takes place within or is characteristic of a country club environment.
-
B.
countryClubType
Indicates that one entity is classified as a specific type or category of country club in relation to another entity.
-
C.
golfCourseUse
Indicates that an entity is used as a golf course or for playing golf.
-
D.
recreationActivitiesSupported
Indicates that an entity provides, allows, or is compatible with certain recreational activities.
-
E.
hasGolfCourse
chosen
Indicates that one entity possesses, contains, or includes a golf course as part of its facilities or attributes.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01b50490e481908eb1d675561fdde2 |
completed | May 11, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_6a01b44b106481908aa98a3f1eb2c119 |
completed | May 11, 2026, 10:49 a.m. |
Created at: May 3, 2026, 4:02 p.m.