Triple

T37018050
Position Surface form Disambiguated ID Type / Status
Subject Snapper Rocks E916135 entity
Predicate hasApproximateWaterTemperatureRange P196689 FINISHED
Object mild to warm subtropical 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: mild to warm subtropical | Statement: [Snapper Rocks, hasApproximateWaterTemperatureRange, mild to warm subtropical]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasApproximateWaterTemperatureRange
Context triple: [Snapper Rocks, hasApproximateWaterTemperatureRange, mild to warm subtropical]
  • A. typicalWaterTemperatureRange chosen
    Indicates the usual lower and upper bounds of water temperature typically associated with or experienced by an entity.
  • B. hasTemperature
    Indicates that an entity possesses or is characterized by a specific temperature value.
  • C. humidityRange
    Indicates the range of humidity values within which a condition, process, or entity is defined, operates, or remains valid.
  • D. temperatureRangeVariant
    Indicates a relationship where one temperature range is a variation or alternative form of another temperature range.
  • E. hasTemperatureRegime
    Indicates that an entity is characterized by or associated with a particular pattern or regime of temperature conditions.
  • 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_69f76e920dc48190acb6bb7ebc4dffab completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fe6c811bcc81908b1e1b1f8bcb071b completed May 8, 2026, 11:06 p.m.
PD Predicate disambiguation batch_69fe6c026d5481908b7a814dcf38c183 completed May 8, 2026, 11:04 p.m.
Created at: May 3, 2026, 4:14 p.m.