Triple
T3002650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemlock Lake |
E81824
|
entity |
| Predicate | shorelineOwnership |
P44588
|
FINISHED |
| Object | largely public utility or protected lands |
—
|
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: largely public utility or protected lands | Statement: [Hemlock Lake, shorelineOwnership, largely public utility or protected lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shorelineOwnership Context triple: [Hemlock Lake, shorelineOwnership, largely public utility or protected lands]
-
A.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
B.
hasShorelineUse
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
C.
hasShorelineUseRestrictions
Indicates that there are specific rules or limitations governing how the shoreline area associated with an entity may be used or developed.
-
D.
shorelineLength
Indicates the total measured extent of a land area’s boundary where it meets a body of water.
-
E.
shoreType
Indicates the kind or classification of a shoreline associated with a body of water or coastal area.
- 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_69ad8b1c4de88190a83b7cefaa1f2842 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a1371c481909e214234afed1a65 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad96180eb08190a524c5f458d41382 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:59 p.m.