Triple

T30412562
Position Surface form Disambiguated ID Type / Status
Subject Tripura Tribal Areas Autonomous District Council E773658 entity
Predicate hasPowerInField P544 FINISHED
Object Land management 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: Land management | Statement: [Tripura Tribal Areas Autonomous District Council, hasPowerInField, Land management]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPowerInField
Context triple: [Tripura Tribal Areas Autonomous District Council, hasPowerInField, Land management]
  • A. hasPower chosen
    Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
  • B. hasAssociatedPower
    Indicates that one entity possesses, is linked to, or is characterized by a particular power or capability.
  • C. hasPowerBase
    Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
  • D. usesPowerFor
    Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
  • E. hasNumberOfPowers
    Indicates the quantity of distinct powers or abilities that an entity possesses.
  • 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_69f22490b8b48190ab10c886a8d58c89 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fdb45537288190b6791078d4a6899f completed May 8, 2026, 10 a.m.
PD Predicate disambiguation batch_69fdb39ad96481908376d7def9fafc13 completed May 8, 2026, 9:57 a.m.
Created at: April 29, 2026, 8:05 p.m.