Triple

T11569232
Position Surface form Disambiguated ID Type / Status
Subject INSAT-2C E274339 entity
Predicate followedBy P78 FINISHED
Object INSAT-2D E277745 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-2D | Statement: [INSAT-2C, followedBy, INSAT-2D]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: INSAT-2D
Context triple: [INSAT-2C, followedBy, INSAT-2D]
  • A. INSAT-2D chosen
    INSAT-2D was an Indian geostationary communications and meteorological satellite in the INSAT-2 series, used for telecommunications, broadcasting, and weather services.
  • B. INSAT-2B
    INSAT-2B is an Indian multipurpose geostationary satellite used for telecommunications, meteorology, and search-and-rescue services as part of the INSAT-2 series.
  • C. INSAT-2C
    INSAT-2C is an Indian geostationary communications satellite in the INSAT-2 series, used for telecommunications, broadcasting, and meteorological services.
  • D. INSAT-2A
    INSAT-2A is an Indian multipurpose geostationary satellite used primarily for telecommunications, broadcasting, and meteorological services.
  • E. INSAT-2E
    INSAT-2E is an Indian multipurpose geostationary satellite used primarily for telecommunications, meteorology, and broadcasting as part of the INSAT-2 series.
  • 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_69d6aae5ac3c81908d2b0a3a665665b2 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d88dd543a48190b834abd8e8ae7b65 completed April 10, 2026, 5:42 a.m.
NED1 Entity disambiguation (via context triple) batch_69f457dc01ec8190a7ee3108d4d95957 completed May 1, 2026, 7:35 a.m.
Created at: April 8, 2026, 9:37 p.m.