Triple

T25477356
Position Surface form Disambiguated ID Type / Status
Subject Production Conditions in Indian Agriculture E638467 entity
Predicate regionAnalyzed P169890 FINISHED
Object rural 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: rural India | Statement: [Production Conditions in Indian Agriculture, regionAnalyzed, rural India]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionAnalyzed
Context triple: [Production Conditions in Indian Agriculture, regionAnalyzed, rural India]
  • A. regionFrom
    Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
  • B. region1
    Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
  • C. regionRecognized
    Indicates that a specific geographic or spatial region has been formally identified and acknowledged as valid or relevant within a given context.
  • D. occupiedRegion
    Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
  • E. regionImplied
    Indicates that a broader or more general region is inferred or assumed from a given, more specific regional reference.
  • 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_69e75db9b964819096802dcf502e577e completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f688d015908190ad5df37030ecf332 completed May 2, 2026, 11:29 p.m.
PD Predicate disambiguation batch_69f68609c0b08190a8e1238a4d97c270 completed May 2, 2026, 11:17 p.m.
PDg Predicate description generation batch_69f688034580819086a0f9100645f8ba completed May 2, 2026, 11:25 p.m.
Created at: April 21, 2026, 2:26 p.m.