Triple

T24616460
Position Surface form Disambiguated ID Type / Status
Subject Saskylakh E609273 entity
Predicate locatedInNaturalZone P110443 FINISHED
Object tundra and forest-tundra zone 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: tundra and forest-tundra zone | Statement: [Saskylakh, locatedInNaturalZone, tundra and forest-tundra zone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInNaturalZone
Context triple: [Saskylakh, locatedInNaturalZone, tundra and forest-tundra zone]
  • A. onlyNaturalHabitatOf
    Indicates that a given location is the sole natural habitat where a particular species or organism occurs in the wild.
  • B. situatedInProtectedArea
    Indicates that an entity is located within the boundaries of a designated protected area (such as a reserve, park, or conservation zone).
  • C. isEcologicalZone
    Indicates that one entity functions as, or is classified as, an ecological zone in relation to another entity.
  • D. naturalRegionOf chosen
    Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
  • E. hasNaturalAreaType
    Indicates that an entity is associated with or classified by a specific type of natural area (e.g., forest, wetland, grassland).
  • 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_69e2c4d1140081909c58667bf68f80c3 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f2be044d4c819094e14eda28d371a7 completed April 30, 2026, 2:27 a.m.
PD Predicate disambiguation batch_69f2a6ca751c8190a040c10d701ecf3a completed April 30, 2026, 12:48 a.m.
Created at: April 18, 2026, 2:31 a.m.