Triple
T6256389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson Lake |
E140176
|
entity |
| Predicate | hasShoreActivity |
P20797
|
FINISHED |
| Object | camping |
—
|
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: camping | Statement: [Wilson Lake, hasShoreActivity, camping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShoreActivity Context triple: [Wilson Lake, hasShoreActivity, camping]
-
A.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
B.
hasShoreFeature
Indicates that a shore or coastline possesses a specific physical or environmental feature.
-
C.
hasInshoreRaces
Indicates that an entity conducts or includes races that take place in inshore or nearshore waters.
-
D.
hasWaterActivity
Indicates that one entity possesses, exhibits, or is characterized by a particular level or type of water-related activity (such as moisture content, water availability, or water-based processes).
-
E.
hasShorelineUse
chosen
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063653910819095f1dc3b90ce77db |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.