Triple
T11001917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceansat-1 |
E260022
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | IRS-P4 |
E264413
|
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: IRS-P4 | Statement: [Oceansat-1, alsoKnownAs, IRS-P4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IRS-P4 Context triple: [Oceansat-1, alsoKnownAs, IRS-P4]
-
A.
IRS-P4
chosen
IRS-P4 is an Indian remote sensing satellite used primarily for ocean and coastal monitoring as part of the IRS (Indian Remote Sensing) satellite series.
-
B.
IRS-P2
IRS-P2 is an Indian remote sensing satellite in the IRS series used primarily for Earth observation and resource monitoring.
-
C.
IRS-P5
IRS-P5 is an Indian remote sensing satellite in the IRS series, designed primarily for cartographic and resource management applications.
-
D.
IRS-P3
IRS-P3 is an Indian remote sensing satellite in the IRS series used primarily for Earth observation and resource monitoring.
-
E.
IRS-P6
IRS-P6, also known as Resourcesat-1, is an Indian Earth observation satellite designed for resource monitoring and management, including agriculture, forestry, and land-use mapping.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d760008190930228fa77b61b8b |
completed | April 9, 2026, 12:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3453d181081908cb58a957f4d1295 |
completed | April 18, 2026, 8:47 a.m. |
Created at: April 8, 2026, 9:25 p.m.