Triple

T7840396
Position Surface form Disambiguated ID Type / Status
Subject Ghagra E181789 entity
Predicate wornInRegion P908 FINISHED
Object North India 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: North India | Statement: [Ghagra, wornInRegion, North India]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wornInRegion
Context triple: [Ghagra, wornInRegion, North India]
  • A. hasRegion
    Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
  • B. usedInRegion chosen
    Indicates that something is utilized or applied within a specific geographic or administrative region.
  • C. foundInRegion
    Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
  • D. placeRegion
    Indicates that a place is located within, or is part of, a larger geographic or administrative region.
  • E. mentionsRegion
    Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
  • 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_69ca8285d6488190a95d4c02d7354b53 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb14c589748190b34d0911d373e194 completed March 31, 2026, 12:26 a.m.
PD Predicate disambiguation batch_69cae91e98988190abd4ece75932c589 completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:47 p.m.