Triple

T532025
Position Surface form Disambiguated ID Type / Status
Subject Andaman and Nicobar Command E12242 entity
Predicate isOnly P3282 FINISHED
Object India’s only tri-service theatre command 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: India’s only tri-service theatre command | Statement: [Andaman and Nicobar Command, isOnly, India’s only tri-service theatre command]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isOnly
Context triple: [Andaman and Nicobar Command, isOnly, India’s only tri-service theatre command]
  • A. isSelective
    Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
  • B. isMostly
    Indicates that one entity constitutes the greater part or majority of another entity in amount, extent, or composition.
  • C. secondOnlyTo
    Indicates that one entity ranks immediately below another in degree, importance, or quality, with only that other entity surpassing it.
  • D. hasSingle chosen
    Indicates that an entity possesses exactly one instance of a specified related entity or attribute.
  • E. isAt
    Indicates that one entity is located at or present in the place or position of another entity.
  • 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_69a4933208e88190891f5debab1b776d completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4985e51908190a34aa82ea9dbee1e completed March 1, 2026, 7:49 p.m.
PD Predicate disambiguation batch_69a494b3e49081909810fa417b31306f completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:32 p.m.