Triple
T28752749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hayden Lake |
E731576
|
entity |
| Predicate | hasShorelineLandUse |
P20797
|
FINISHED |
| Object | residential development |
—
|
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: residential development | Statement: [Hayden Lake, hasShorelineLandUse, residential development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShorelineLandUse Context triple: [Hayden Lake, hasShorelineLandUse, residential development]
-
A.
hasShorelineUse
chosen
Indicates that a geographic area or property is used for a particular type of activity or purpose along its shoreline.
-
B.
hasShorelineUseRestrictions
Indicates that there are specific rules or limitations governing how the shoreline area associated with an entity may be used or developed.
-
C.
shorelineIncludes
Indicates that a shoreline spatially contains or encompasses a specified coastal feature or segment.
-
D.
hasShorelineMaterial
Indicates that a geographic feature’s shoreline is composed of or characterized by a specified material.
-
E.
hasCoastalFunction
Indicates that something serves a role, purpose, or activity specifically related to the coast or coastal areas.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 28, 2026, 6:08 a.m.