Triple

T26289728
Position Surface form Disambiguated ID Type / Status
Subject Maharashtra E661233 entity
Predicate borderDisputeLegalApproach P105640 FINISHED
Object petitioned Supreme Court of 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: petitioned Supreme Court of India | Statement: [Maharashtra, borderDisputeLegalApproach, petitioned Supreme Court of India]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderDisputeLegalApproach
Context triple: [Maharashtra, borderDisputeLegalApproach, petitioned Supreme Court of India]
  • A. borderDisputeResolvedBy
    Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
  • B. borderDisputesWith
    Indicates that there are contested or unresolved boundary claims between two entities.
  • C. borderIssue chosen
    Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
  • D. associatedTerritoryDispute
    Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
  • E. frontierDispute
    Indicates a conflict or disagreement between entities over the location, control, or status of a shared boundary or border.
  • 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_69ee812bbd448190be4d7478b057990a completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc53f4f881908dcc698687bbb64d completed May 3, 2026, 7:42 a.m.
Created at: April 26, 2026, 10:07 p.m.