Triple

T14428497
Position Surface form Disambiguated ID Type / Status
Subject Third Lake E357757 entity
Predicate hasShorelineOwnership P44588 FINISHED
Object predominantly private 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: predominantly private | Statement: [Third Lake, hasShorelineOwnership, predominantly private]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasShorelineOwnership
Context triple: [Third Lake, hasShorelineOwnership, predominantly private]
  • A. shorelineOwnership chosen
    Indicates that one entity holds legal or recognized ownership rights over a stretch of shoreline associated with another entity or location.
  • 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. hasLongShoreline
    Indicates that an entity possesses an extensive or unusually long shoreline relative to typical cases.
  • E. hasShorelineCountry
    Indicates that a country possesses a coastline or land boundary directly adjacent to a particular body of water or coastal region.
  • 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_69d8279402a88190821ffa39ae15bccf completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91154de881909266ae88d1545685 completed April 14, 2026, 7:10 p.m.
PD Predicate disambiguation batch_69de5c30467881908e770e3940295641 completed April 14, 2026, 3:24 p.m.
Created at: April 10, 2026, 1:18 a.m.