Triple
T8502542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plantation Preserve Golf Course & Club |
E201254
|
entity |
| Predicate | hasWalkingTrailsAdjacent |
P12052
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Plantation Preserve Golf Course & Club, hasWalkingTrailsAdjacent, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkingTrailsAdjacent Context triple: [Plantation Preserve Golf Course & Club, hasWalkingTrailsAdjacent, yes]
-
A.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
B.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
-
C.
hasNearbyTrail
chosen
Indicates that one entity is located close to or within a short distance of a trail.
-
D.
hasShorelineTrail
Indicates that a location or body of water is connected to or bordered by a trail that runs along its shoreline.
-
E.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe59c413881909513d8a9d52333c0 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.