Triple
T36619289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aryabhata |
E903687
|
entity |
| Predicate | launchArrangement |
P190717
|
FINISHED |
| Object | launched under Indo-Soviet space cooperation |
—
|
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: launched under Indo-Soviet space cooperation | Statement: [Aryabhata, launchArrangement, launched under Indo-Soviet space cooperation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchArrangement Context triple: [Aryabhata, launchArrangement, launched under Indo-Soviet space cooperation]
-
A.
launchAs
Indicates that one entity initiates or starts another entity in a particular role, mode, or form.
-
B.
launchesFrom
Indicates that an object or agent initiates its movement, operation, or departure starting at a specified location or source.
-
C.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
-
D.
launchDestination
Indicates the target location or endpoint toward which something is launched or sent.
-
E.
launchProcedure
Indicates the process or sequence of actions required to initiate or start an operation, system, or mission.
- 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_69f76e6960e4819092047756ceb9a17e |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:11 p.m.