Triple
T2235691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thompson Lake |
E49273
|
entity |
| Predicate | hasShorelineDevelopment |
P25009
|
FINISHED |
| Object | seasonal camps |
—
|
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: seasonal camps | Statement: [Thompson Lake, hasShorelineDevelopment, seasonal camps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShorelineDevelopment Context triple: [Thompson Lake, hasShorelineDevelopment, seasonal camps]
-
A.
hasWaterfrontDevelopment
chosen
Indicates that a location or property includes or is associated with constructed developments directly along or adjacent to a body of water.
-
B.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
C.
hasShorelineCommunity
Indicates that a place or region includes or is associated with a community located along its shoreline.
-
D.
hasShorelineUseRestrictions
Indicates that there are specific rules or limitations governing how the shoreline area associated with an entity may be used or developed.
-
E.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc093ba0c819091df09a0e018fce1 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.