Triple
T23496455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brothers Water |
E571715
|
entity |
| Predicate | hasNearbyCampsite |
P79315
|
FINISHED |
| Object | Sykeside campsite |
—
|
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: Sykeside campsite | Statement: [Brothers Water, hasNearbyCampsite, Sykeside campsite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCampsite Context triple: [Brothers Water, hasNearbyCampsite, Sykeside campsite]
-
A.
nearbyCampground
chosen
Indicates that one location has a campground situated close to it in geographic proximity.
-
B.
hasNearbyPOWCampSite
Indicates that one location is situated close to a prisoner-of-war (POW) camp site.
-
C.
hasCampground
Indicates that one entity provides, contains, or is associated with a campground facility or area for another entity.
-
D.
hasNearbyTrailheadFor
Indicates that one location has a trailhead situated close enough to serve as a convenient access point for another location.
-
E.
hasNearbyWildernessArea
Indicates that a wilderness area is located within a close geographic proximity to the referenced place or entity.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7e00384819092729319a378d4ab |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.