Triple

T17528133
Position Surface form Disambiguated ID Type / Status
Subject Pleasant Lake (water body) E426856 entity
Predicate hasSurroundingFeatureType P85343 FINISHED
Object geographic features 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: geographic features | Statement: [Pleasant Lake (water body), hasSurroundingFeatureType, geographic features]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSurroundingFeatureType
Context triple: [Pleasant Lake (water body), hasSurroundingFeatureType, geographic features]
  • A. hasSurroundings
    Indicates that an entity is located within or encircled by a particular environment, context, or set of surrounding elements.
  • B. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • C. hasNearbyLandscapeType chosen
    Indicates that one entity is located close to, or in the vicinity of, a particular type of landscape.
  • D. hasSurfaceFeatureState
    Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
  • E. includesFeatureTypes
    Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
  • 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_69d889de677081909b22d2657b1f0292 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e452d81a808190ab38831ea5b73b74 completed April 19, 2026, 3:58 a.m.
PD Predicate disambiguation batch_69e3b4f8b9888190aa8a45e09acf4319 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:49 a.m.