Triple

T12777410
Position Surface form Disambiguated ID Type / Status
Subject INSAT-3DS E305412 entity
Predicate successorOf P78 FINISHED
Object INSAT-3DR E303872 NE 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: INSAT-3DR | Statement: [INSAT-3DS, successorOf, INSAT-3DR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: INSAT-3DR
Context triple: [INSAT-3DS, successorOf, INSAT-3DR]
  • A. INSAT-3DR chosen
    INSAT-3DR is an Indian geostationary weather satellite designed to provide advanced meteorological observations, search and rescue services, and data relay capabilities.
  • B. INSAT-3DS
    INSAT-3DS is an Indian geostationary meteorological and communication satellite in the INSAT series, designed to support weather forecasting, disaster warning, and environmental monitoring.
  • C. INSAT-3D
    INSAT-3D is an Indian advanced meteorological satellite designed to provide enhanced weather forecasting, disaster warning, and search-and-rescue services.
  • D. INSAT-3C
    INSAT-3C is an Indian geostationary communications satellite in the INSAT series, used for telecommunication, broadcasting, and meteorological services.
  • E. INSAT-3E
    INSAT-3E is an Indian communications satellite in the INSAT series used primarily for telecommunication and broadcasting services.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d7bdf2b43c819098ae5aa68e61ea58 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e595e008190b42dff3012d17d66 completed April 10, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f79d3188f88190aafbb1cf97317dc8 completed May 3, 2026, 7:08 p.m.
Created at: April 9, 2026, 5:29 p.m.