Triple

T3631528
Position Surface form Disambiguated ID Type / Status
Subject Indus Gorge in the Himalayas E76965 entity
Predicate carvedThrough P49679 FINISHED
Object high Himalayan ranges 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: high Himalayan ranges | Statement: [Indus Gorge in the Himalayas, carvedThrough, high Himalayan ranges]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: carvedThrough
Context triple: [Indus Gorge in the Himalayas, carvedThrough, high Himalayan ranges]
  • A. carvedInto
    Indicates that one entity has been shaped, cut, or sculpted so that it takes the form or likeness of another entity.
  • B. hasCarving
    Indicates that one entity features or contains a carved design, inscription, or sculpted detail that is associated with or applied to another entity.
  • C. carvedBy
    Indicates that one entity has been shaped, cut, or sculpted from a material by another entity through a carving process.
  • D. hasBranchCarvings
    Indicates that an entity (such as a tree or wooden object) possesses carvings or engravings specifically on its branches.
  • E. hasCarvings
    Indicates that one entity features or contains carved designs or engravings on its surface, created by another entity or process.
  • F. None of above. chosen

Provenance (4 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_69ad85dc03948190b35b7189e4175bcc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc30136e88190922bb542971b5239 completed March 8, 2026, 6:42 p.m.
PD Predicate disambiguation batch_69adb8410a5881909c94818d7060b2b0 completed March 8, 2026, 5:56 p.m.
PDg Predicate description generation batch_69adb902e61c81908f10494f828e260f completed March 8, 2026, 5:59 p.m.
Created at: March 8, 2026, 3:23 p.m.