Triple
T18708462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandon Dunes Golf Resort |
E457433
|
entity |
| Predicate | walkingPolicy |
P132378
|
FINISHED |
| Object | caddies available |
—
|
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: caddies available | Statement: [Bandon Dunes Golf Resort, walkingPolicy, caddies available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkingPolicy Context triple: [Bandon Dunes Golf Resort, walkingPolicy, caddies available]
-
A.
walkInPolicy
Indicates that an entity allows or operates under a policy where individuals can arrive and be served without a prior appointment.
-
B.
walkThrough
Indicates moving through or along the interior or extent of something, typically traversing a space or environment from one side or point to another.
-
C.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
D.
hasWalkingAllowed
Indicates that walking is permitted within or across the referenced area or context.
-
E.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e484133ee48190a80f1889d79f34c9 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:50 a.m.