Triple
T12292671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INSAT-4A |
E293002
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | INSAT-4B |
E294161
|
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-4B | Statement: [INSAT-4A, followedBy, INSAT-4B]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: INSAT-4B Context triple: [INSAT-4A, followedBy, INSAT-4B]
-
A.
INSAT-4B
chosen
INSAT-4B is an Indian communications satellite in the INSAT series, used primarily for telecommunications, broadcasting, and meteorological services.
-
B.
INSAT-4A
INSAT-4A is an Indian communications satellite in the INSAT series, used primarily for telecommunications and broadcasting services.
-
C.
INSAT-4E
INSAT-4E is an Indian communications satellite in the INSAT series, designed to provide telecommunication, broadcasting, and related services.
-
D.
INSAT-4CR
INSAT-4CR is an Indian communications satellite in the INSAT series, launched by ISRO to provide telecommunication and broadcasting services.
-
E.
INSAT-3B
INSAT-3B is an Indian communications satellite in the INSAT series used for telecommunication, broadcasting, and meteorological 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d22ba488190914342fa7e69e159 |
completed | April 10, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6fef515488190957a69e1cc901d65 |
completed | May 3, 2026, 7:53 a.m. |
Created at: April 8, 2026, 9:52 p.m.