Triple
T36487158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LISS-I sensor |
E898963
|
entity |
| Predicate | usedOnSatelliteSeries |
P43140
|
FINISHED |
| Object | Indian Remote Sensing satellites |
—
|
NE NERFINISHED |
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: Indian Remote Sensing satellites | Statement: [LISS-I sensor, usedOnSatelliteSeries, Indian Remote Sensing satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnSatelliteSeries Context triple: [LISS-I sensor, usedOnSatelliteSeries, Indian Remote Sensing satellites]
-
A.
usedWithSpacecraftSeries
chosen
Indicates that something is employed or associated in use with a particular series or family of spacecraft.
-
B.
operatesOnSatellite
Indicates that an entity performs operations or exercises control over a satellite.
-
C.
satelliteSeries
Indicates that one entity is a series or family grouping of related satellites to which another satellite or mission belongs.
-
D.
usedWithSpacecraft
Indicates that something is employed or operated in conjunction with a spacecraft.
-
E.
usedSatelliteDistribution
Indicates that an entity employed satellite-based channels or infrastructure to distribute something (such as content, data, or services).
- F. None of above.
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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bccf05bc8190b61fdb2b2a315811 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.