Triple

T2294647
Position Surface form Disambiguated ID Type / Status
Subject Subansiri River E51581 entity
Predicate hasAlternateClassification P14654 FINISHED
Object trans-Himalayan river 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: trans-Himalayan river | Statement: [Subansiri River, hasAlternateClassification, trans-Himalayan river]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAlternateClassification
Context triple: [Subansiri River, hasAlternateClassification, trans-Himalayan river]
  • A. areClassifiedBy
    Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
  • B. isClassifiedUnder
    Indicates that one entity is categorized or grouped within a broader class, type, or category represented by another entity.
  • C. isSometimesClassifiedAs chosen
    Indicates that an entity is occasionally, but not consistently or universally, categorized under a particular type or class.
  • D. isAlternativeTo
    Indicates that one entity can serve as a substitute or different option in place of another.
  • E. hasLCClassification
    Indicates that an entity is assigned a specific Library of Congress Classification code representing its subject or shelving category.
  • 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_69a88b09c644819090b503456d96bf70 completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abcd0e42248190ada33b84d75caa64 completed March 7, 2026, 7 a.m.
PD Predicate disambiguation batch_69abc589295c819092989820c2b4e9d8 completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:49 p.m.