Triple

T8559731
Position Surface form Disambiguated ID Type / Status
Subject Yamunotri Temple E202659 entity
Predicate traditionalAccess P83627 FINISHED
Object mountain trek 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: mountain trek | Statement: [Yamunotri Temple, traditionalAccess, mountain trek]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionalAccess
Context triple: [Yamunotri Temple, traditionalAccess, mountain trek]
  • A. traditionalSee
    Indicates that one entity perceives or views another entity in a conventional or customary manner, following established norms or traditions.
  • B. traditionalEnd
    Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
  • C. traditionalStyle
    Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
  • D. traditionalBase
    Indicates that one entity serves as the customary or historically established foundation or basis for another.
  • E. traditionalStatus
    Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to another entity.
  • 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_69ca8326e6c881908ff720d6abaebdc5 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbe949974c8190a75d9c767ca5fa5a completed March 31, 2026, 3:33 p.m.
PD Predicate disambiguation batch_69cbd1160fcc8190aa380a73610af731 completed March 31, 2026, 1:50 p.m.
PDg Predicate description generation batch_69cbe30e37ac8190b685df36274602b5 completed March 31, 2026, 3:06 p.m.
Created at: March 30, 2026, 6:20 p.m.