Triple

T11291218
Position Surface form Disambiguated ID Type / Status
Subject INSAT-1D E267327 entity
Predicate followedBy P78 FINISHED
Object INSAT-2A E271253 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-2A | Statement: [INSAT-1D, followedBy, INSAT-2A]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: INSAT-2A
Context triple: [INSAT-1D, followedBy, INSAT-2A]
  • A. INSAT-2A chosen
    INSAT-2A is an Indian multipurpose geostationary satellite used primarily for telecommunications, broadcasting, and meteorological 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-1B
    INSAT-1B was an early Indian multipurpose geostationary satellite used for telecommunications, broadcasting, and meteorological services as part of the INSAT program.
  • E. INSAT-2D
    INSAT-2D was an Indian geostationary communications and meteorological satellite in the INSAT-2 series, used for telecommunications, broadcasting, and weather 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_69d6aac993a08190a6f36445ebaf9a43 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e989fdac81909a4a75f1f68b55c6 completed April 9, 2026, 6:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5e8a4322c8190a30e460892123579 completed April 20, 2026, 8:49 a.m.
Created at: April 8, 2026, 9:32 p.m.