Triple
T38479568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PSLV-C6 |
E915633
|
entity |
| Predicate | secondaryPayloadOperator |
P201247
|
FINISHED |
| Object | ISRO |
—
|
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: ISRO | Statement: [PSLV-C6, secondaryPayloadOperator, ISRO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryPayloadOperator Context triple: [PSLV-C6, secondaryPayloadOperator, ISRO]
-
A.
secondaryPayload
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
-
B.
secondRelayOperatedBy
Indicates that a second relay device is controlled or actuated by a specified operator or system.
-
C.
secondaryCargo
Indicates that an entity serves as an additional or auxiliary cargo associated with a primary shipment or load.
-
D.
missionOperator
Indicates that one entity is responsible for operating, managing, or controlling a mission involving another entity.
-
E.
primaryCargoOperator
Indicates that an entity serves as the main organization responsible for operating or managing the cargo-related activities of another entity.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
| PDg | Predicate description generation | batch_69ffe01be6e88190ac0742a5f74e769e |
completed | May 10, 2026, 1:32 a.m. |
Created at: May 3, 2026, 4:31 p.m.