Triple
T36514850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-C2 |
E900007
|
entity |
| Predicate | Oceansat-1Purpose |
P186033
|
FINISHED |
| Object | ocean colour and wind vector observation |
—
|
LITERAL 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: ocean colour and wind vector observation | Statement: [PSLV-C2, Oceansat-1Purpose, ocean colour and wind vector observation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Oceansat-1Purpose Context triple: [PSLV-C2, Oceansat-1Purpose, ocean colour and wind vector observation]
-
A.
satelliteType
Indicates that one entity is classified as a specific type or category of satellite relative to another entity.
-
B.
typeOfSatelliteOperated
Indicates that one entity operates or manages a satellite of a specified type or category in relation to another entity.
-
C.
firstSuccessfulSatellite
Indicates that the subject entity is the earliest or initial satellite to have successfully achieved its intended operational status or mission.
-
D.
satellite
Indicates that one entity orbits and is gravitationally bound to another, typically larger, central body.
-
E.
operatesOnSatellite
Indicates that an entity performs operations or exercises control over a satellite.
- F. None of above. chosen
Provenance (4 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:10 p.m.