Triple
T18708435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandon Dunes Golf Resort |
E457433
|
entity |
| Predicate | numberOf18HoleCourses |
P21556
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Bandon Dunes Golf Resort, numberOf18HoleCourses, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOf18HoleCourses Context triple: [Bandon Dunes Golf Resort, numberOf18HoleCourses, 5]
-
A.
numberOfGolfCourses
chosen
Indicates the total count of golf courses associated with a given entity.
-
B.
hasGolfCourse
Indicates that one entity possesses, contains, or includes a golf course as part of its facilities or attributes.
-
C.
hasGolfCourseCluster
Indicates that an entity is associated with or contains a group or concentration of golf courses in a particular area.
-
D.
designedGolfCourses
Indicates that one entity is the architect or creator responsible for designing the layout and features of one or more golf courses associated with another entity.
-
E.
hasInnerTurfCourse
Indicates that something (typically a race track or stadium) possesses an inner turf course located within its main track or field.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56719383481909d68c9e873ca0800 |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.