Triple
T18708436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandon Dunes Golf Resort |
E457433
|
entity |
| Predicate | numberOfPar3Courses |
P68172
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Bandon Dunes Golf Resort, numberOfPar3Courses, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPar3Courses Context triple: [Bandon Dunes Golf Resort, numberOfPar3Courses, 2]
-
A.
golfCoursePar
Indicates the standard number of strokes a skilled golfer is expected to take to complete a particular golf course or hole.
-
B.
numberOfGolfCourses
Indicates the total count of golf courses associated with a given entity.
-
C.
typicalCoursePar
Indicates that one course is a typical or standard parallel (i.e., alternative but equivalent) course to another within a curriculum or program.
-
D.
hasPar3Course
chosen
Indicates that an entity (such as a golf facility or location) includes or is associated with a par-3 golf course.
-
E.
hasCoursePar
Indicates that one course is a parent or higher-level course in relation to another course, such as a prerequisite or overarching course.
- 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.