Triple
T11886648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSAT-3B |
E282799
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | INSAT-3C |
E285708
|
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-3C | Statement: [INSAT-3B, followedBy, INSAT-3C]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: INSAT-3C Context triple: [INSAT-3B, followedBy, INSAT-3C]
-
A.
INSAT-3C
chosen
INSAT-3C is an Indian geostationary communications satellite in the INSAT series, used for telecommunication, broadcasting, and meteorological services.
-
B.
INSAT-3A
INSAT-3A is an Indian multipurpose geostationary satellite used for telecommunications, television broadcasting, meteorology, and search-and-rescue services.
-
C.
INSAT-3E
INSAT-3E is an Indian communications satellite in the INSAT series used primarily for telecommunication and broadcasting services.
-
D.
INSAT-3B
INSAT-3B is an Indian communications satellite in the INSAT series used for telecommunication, broadcasting, and meteorological services.
-
E.
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.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a13370819086386fecb99e4f0b |
completed | April 10, 2026, 10:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684c71548819081af6734b8b7279a |
completed | May 2, 2026, 11:12 p.m. |
Created at: April 8, 2026, 9:44 p.m.