Triple
T36514846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-C2 |
E900007
|
entity |
| Predicate | internationalPayloads |
P197685
|
FINISHED |
| Object | KITSAT-3 |
—
|
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: KITSAT-3 | Statement: [PSLV-C2, internationalPayloads, KITSAT-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internationalPayloads Context triple: [PSLV-C2, internationalPayloads, KITSAT-3]
-
A.
missionPayload
Indicates that an entity serves as the payload or carried cargo for a particular mission.
-
B.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
-
C.
communicationsPayload
Indicates that an entity carries or contains equipment, data, or components specifically intended for communication purposes.
-
D.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
E.
launchesPayloadType
Indicates that an entity initiates the deployment or sending of a payload of a specified type.
- 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_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
| PDg | Predicate description generation | batch_69fea1f4daa88190bd3cc1ace684e77f |
completed | May 9, 2026, 2:54 a.m. |
Created at: May 3, 2026, 4:10 p.m.