Triple

T27374178
Position Surface form Disambiguated ID Type / Status
Subject Van Duzen River E691014 entity
Predicate hasVegetationTypeAlong P953 FINISHED
Object redwood forest 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: redwood forest | Statement: [Van Duzen River, hasVegetationTypeAlong, redwood forest]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasVegetationTypeAlong
Context triple: [Van Duzen River, hasVegetationTypeAlong, redwood forest]
  • A. vegetationType chosen
    Indicates the specific kind or category of plant cover or flora that characterizes a given area or environment.
  • B. hasVegetationRole
    Indicates that an entity participates in or is assigned a specific functional role related to vegetation (such as growth, maintenance, or impact on plant life).
  • C. hasVegetationBeltBelow
    Indicates that an entity possesses a distinct band or zone of vegetation located directly beneath it or below a specified reference level.
  • D. hasVegetationLayer
    Indicates that an entity possesses a distinct layer or cover of vegetation as part of its structure or surface.
  • E. hasVegetationContext
    Indicates that an entity is associated with, occurs within, or is characterized by a particular type or condition of vegetation.
  • 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_69ef52022538819081f873d0c84a6dd6 completed April 27, 2026, 12:09 p.m.
NER Named-entity recognition batch_69f661b58ac48190907b6c6e9ccc2c59 completed May 2, 2026, 8:42 p.m.
PD Predicate disambiguation batch_69f660eea4648190b0d5e24293607813 completed May 2, 2026, 8:39 p.m.
Created at: April 27, 2026, 12:20 p.m.